feat(): Avoid IAM service role name conflicts when used with terraform-aws-elastic-beanstalk-environment#60
Merged
aknysh merged 1 commit intocloudposse:mainfrom Aug 8, 2025
Conversation
Member
|
/terratest |
aknysh
approved these changes
Aug 8, 2025
Member
|
thanks @cilasbeltrame |
|
These changes were released in v0.12.1. |
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.
what
When this module is used together with cloudposse/terraform-aws-elastic-beanstalk-environment, the environment module already creates an Elastic Beanstalk service role (see main.tf#L34).
This PR updates our module to use a dedicated IAM role for the lifecycle policy, preventing a name collision with the existing service role.
why
references
Cloud Posse environment module creating the EB service role: main.tf#L34