-
Notifications
You must be signed in to change notification settings - Fork 820
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Param bound #7502
Param bound #7502
Conversation
…tem-config-manager.js (aws-amplify#7053)
Codecov Report
@@ Coverage Diff @@
## master #7502 +/- ##
==========================================
+ Coverage 52.68% 52.79% +0.11%
==========================================
Files 519 523 +4
Lines 26012 26137 +125
Branches 5085 5113 +28
==========================================
+ Hits 13704 13800 +96
- Misses 11334 11368 +34
+ Partials 974 969 -5
Continue to review full report at Codecov.
|
👋 Hi, this pull request was referenced in the v5.0.0 release! Check out the release notes here https://github.com/aws-amplify/amplify-cli/releases/tag/v5.0.0. |
…(ref aws-amplify#4618) * fix(amplify-provider-awscloudformation): fix tests failing due to system-config-manager.js (aws-amplify#7053) * feat: s3 sse by default * chore: fix init push issue * chore: cleanup * test: whole lotta tests * test: update nondeterministic test * fix: serialize modifiers and improve test error handling * fix: add parameterization to ResourceModifier * fix: add type to sig * test: update test with new modifier structure * test: fix test * feat: add permission boundary to IAM roles * fix: update iam role modifier * test: add e2e test for perm bound * test: add unit tests for perm bound modifier * fix: fix regex * feat: switch to env-specific config * chore: dumping env perm bound changes * feat: fixup env-specific config and add headless support * chore: cleaning up things * test: more unit tests and e2e test * test: small test tweaks * chore: reverting some unintentional linting changes * fix: add update to env help text * test: add mock * chore: address PR comments * chore: use module var instead of global var * chore: rename permission boundary -> permissions boundary * fix: merge tpi instead of overwrite * chore: remove newline * fix: load creds for new env when checking policy * fix: test fixes * test: fix unit tests * test: fix profile selection * fix: change permissions boundary success text Co-authored-by: Raj Rajhans <[email protected]>
Description of changes
Reopening #7144
Adds a new advanced project configuration option to specify a permissions boundary that will be applied to all IAM roles in the project. This is broken into 3 components:
amplify-cli-core
amplify configure project
that writes the boundary to the state managerIssue #, if available
#4618
Description of how you validated changes
Manually validated as well as unit tested and e2e tested
Checklist
yarn test
passesadd permission boundary docs docs#3157
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.