Allow role chaining for configuring aws credentials #73
+6
−0
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
mcalhoun
previously approved these changes
May 6, 2024
goruha
reviewed
May 6, 2024
|
@mfuhrmeisterDM could you also update documentation |
this is done. I updated also the README.md with |
nitrocode
changed the title
added 2 commits
July 1, 2024 16:36
use present progressive name reset credentials for 2nd assume role call if role chaining
mfuhrmeisterDM
force-pushed
the
role-chaning
branch
from
437aa27 to
5e81352
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.
what
allow to set role chaining for configuring aws credentials
why
We need role chaining because the github runner is already authenticated via web token.