Merged
Conversation
bvigar
approved these changes
Jan 7, 2026
bvigar
left a comment
bvigar
left a comment
There was a problem hiding this comment.
LGTM... nothing needs to be updated to use this renamed IAM role?
Contributor
Author
Nope, just the name, everything else is referencing the arn |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
Since IAM roles are shared across different regions, renaming the IAM role name to be more unique to avoid potential name conflict.
What type of PR is this? (only check one)
feat)fix)refactor)doc)Does this PR introduce any breaking changes?
Does the PR title type prefix match the selected type?