Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

name collision in the terraform output #289

Closed
hellupline opened this issue Aug 9, 2016 · 4 comments
Closed

name collision in the terraform output #289

hellupline opened this issue Aug 9, 2016 · 4 comments
Assignees
Labels
area/terraform Issues or PRs related to the Terraform target P0
Milestone

Comments

@hellupline
Copy link

the resources "aws_security_group_rule" have a "default" name, which conflicts with other clusters created with terraform

@justinsb justinsb added this to the 1.3.0 milestone Aug 15, 2016
@justinsb
Copy link
Member

I thought I understood this, but I'm now not sure I do...

The security groups are named uniquely (incorporating the cluster name). The security group rules do not incorporate the cluster name, but these are "virtual objects" - the name does not render into the AWS API.

I guess this would cause a problem if you took two TF cluster outputs, and rendered them both in the same TF run (e.g. by merging the directories). Is that how you are seeing the problem? And if not, how can I reproduce it?

@chrislovecnm
Copy link
Contributor

@hellupline we have not heard back from you ... bump

@chrislovecnm
Copy link
Contributor

We have PR inbound thay may help with this ... I am looking through issues to test against #1183 - no promises but we need to test.

@justinsb justinsb modified the milestones: 1.4.4, 1.5.0 Dec 28, 2016
@justinsb justinsb added the area/terraform Issues or PRs related to the Terraform target label Jan 7, 2017
@justinsb
Copy link
Member

justinsb commented Jan 7, 2017

Haven't heard anything here. I believe the problem must be when you have 2 kops-generated terraform output files, in the same TF "universe". Then the rules will have the same name.

I think this is the problem that modules are supposed to solve, so I am going to close as a duplicate of #1026, and also opened #1381

Closing, but if there's something else, let's reopen.

@justinsb justinsb closed this as completed Jan 7, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/terraform Issues or PRs related to the Terraform target P0
Projects
None yet
Development

No branches or pull requests

3 participants