Allow wildcards in AssumeRole #21741
Open
Conversation
This file contains hidden or 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
calvn
reviewed
Jul 10, 2023
bdwyertech
force-pushed
the
aws_assumerole_glob
branch
from
1c740f9 to
f6e4378
Compare
Signed-off-by: Brian Dwyer <[email protected]>
bdwyertech
force-pushed
the
aws_assumerole_glob
branch
from
f6e4378 to
5366f3a
Compare
|
@bdwyertech is attempting to deploy a commit to the HashiCorp Team on Vercel. A member of the Team first needs to authorize it. |
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.
Allow globs in AWS AssumeRole credentials. Have a large, dynamic AWS environment and would prefer to avoid a constantly changing, 1000+ string slice.
For more context: https://discuss.hashicorp.com/t/vault-aws-assumerole-wildcards/55889