Skip to content

Conversation

@egarbi
Copy link
Contributor

@egarbi egarbi commented Mar 27, 2018

When modifying default tg the new one need to be created for listener be able to use it and terraform can destroy the old one later

@brandonjbjelland
Copy link
Contributor

brandonjbjelland commented Mar 27, 2018

Hey again @egarbi . I'm wondering if this actually fixes the problem in #57 . Imagining a create_before_destroy scenario here, I'm wondering if name conflicts between the old and new target groups also raise errors (for instance if backend_port were the change). If you've tested your branch and making changes to the target group works, I'll go ahead with the test and merge.

@egarbi
Copy link
Contributor Author

egarbi commented Mar 28, 2018

@brandoconnor you're right, this only fix the case when name changes, all other attributes will fail with:

aws_lb_target_group.main: Error creating LB Target Group: DuplicateTargetGroupName: A target group with the same name 'default-uat' exists, but with different settings

@egarbi
Copy link
Contributor Author

egarbi commented Mar 28, 2018

@brandoconnor I would say this is better than nothing, With this, you can change at least name without this you can change nothing. I can figure now a permanent solution. Don't know mate, you're the expert here. It's up to you. Thanks for this module.

@brandonjbjelland
Copy link
Contributor

The change is appreciated, I just think we need to be clear in the docs about the caveat and how to do a workaround.

I've vetted the change and added some extra bits to the docs and tests to incorporate it. Merging now.

@brandonjbjelland brandonjbjelland merged commit 833b297 into terraform-aws-modules:master Mar 29, 2018
@egarbi egarbi deleted the create_before_destroy_tg branch March 29, 2018 13:04
@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 16, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants