Add developer permissions to manage secrets in CfnStack namespace #30377
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I've already manually applied the change listed here to the |
wjordan
force-pushed
the
cfnstack-secret-permissions
branch
from
38343ee
to
bf77a90
Compare
[ci skip]
wjordan
force-pushed
the
cfnstack-secret-permissions
branch
from
bf77a90
to
94f2ed0
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This extra permission is needed to be able to create adhoc instances from
Developerfederated role via the dev-permissionCloudFormationServiceservice role. The namespace is used by theAWS::SecretsManager::Secretresource namedDatabaseSecretin the cloudformation stack template.