NestedStack: more mening full diff log output
- Dominant language
- TypeScript
- Stars
- 12.9k
- Forks
- 4.6k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 83
Description
### Describe the feature
Need a way to get diff logs out for NestedStack before i deploy CDK code to AWS
### Use Case
Today when you are using multi-stacks in your CDK code its showing the diff before you will deploy, when you start using NestedStack this diff become very problematic becures its only referac til the NestedStach hash and not the full diff list over changes inside NestedStacks
The biggest issue here its if you don't can get this logs out you are working in a huge black-box when you are using NestedStack.
### Proposed Solution
**Solution num 1:**
Use the diff log hash-key for NestedStack resoruces to read the changes out
`cdk diff --nestedStackHash {diff-hash-key}`
**Solution num 2:**
sending falg with to return all NestedStack logs back in the console
`cdk diff --includeNestedStackLog`
**Solution num 3:**
Support NestedStack with full output to json file so its can be manally parsed.
`cdk diff --dumpFullJsonLog --includeNestedStack`
### Other Information
_No response_
### Acknowledgements
- [ ] I may be able to implement this feature request
- [ ] This feature might incur a breaking change
### CDK version used
2.24.1 (build 585f9ca)
### Environment details (OS name and version, etc.)
macOS 12.3.1
Contributor guide
Research direction
No implementation files or tests are named. Start by tracing the existing `cdk diff` NestedStack output and reviewing the three proposed CLI and output approaches. Done means an agreed, tested way to expose the complete set of NestedStack changes before deployment rather than only the hash.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, typescript
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100