-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
aws_autoscaling_group - throw an error when you define a tag twice #6375
Comments
This was held over in the core repository originally because there was no way to validate this at the time. Now that we have |
Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label. If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you! |
bump |
Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label. If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
This issue was originally opened by @jjshoe as hashicorp/terraform#2270. It was migrated here as a result of the provider split. The original body of the issue is below.
https://www.terraform.io/docs/providers/aws/r/autoscaling_group.html
If you do a tag twice, and tell it to propagate in one, and not the other, you get random results in how the group is actually made. Should probably detect and error on this
The text was updated successfully, but these errors were encountered: