iam: Role.customizeRoles should print the report to stdout
- Dominant language
- TypeScript
- Stars
- 12.9k
- Forks
- 4.6k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 83
Description
### Describe the feature
Currently when you use `Role.customizeRoles` the report is generated in a file within `cdk.out`. This is not very intuitive. We should log the human readable report to stdout and point them to `cdk.out` for the files (both human and machine readable).
### Use Case
It is currently confusing and not clear to the user where the report is located. It also doesn't make too much sense to have to go to a file to find the human readable report.
### Proposed Solution
_No response_
### Other Information
_No response_
### Acknowledgements
- [X] I may be able to implement this feature request
- [ ] This feature might incur a breaking change
### CDK version used
2.78.0
### Environment details (OS name and version, etc.)
any
Contributor guide
Research direction
Start at the Role.customizeRoles entry point and trace how the human-readable and machine-readable reports are generated under cdk.out. Review the existing tests for this API, then verify that the human-readable report is printed to stdout while users are directed to the cdk.out files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100