fix(aws): fix ensureRoleRaw to skip role creation when cached role is found #1346
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
… found Before the commit fe8a7a4, initialization process skips creating default role if the cached lambda role is found. Currently it always tries to create role, so it fails if the User is not allowed to create a role. We want to minimize the privilege, by creating the cached role beforehand.
|
@acchou Could you take a look? |
|
@acchou Gentle ping? |
|
@acchou Thanks for merging. I'd like to see a new release. |
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.
Before the commit fe8a7a4, initialization process skips creating default role if the cached lambda role is found. Currently it always tries to create role, so it fails if the User is not allowed to create a role. We want to minimize the privilege, by creating the cached role beforehand.