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

aws_autoscaling_group - throw an error when you define a tag twice #6375

Closed
ghost opened this issue Nov 6, 2018 · 5 comments
Closed

aws_autoscaling_group - throw an error when you define a tag twice #6375

ghost opened this issue Nov 6, 2018 · 5 comments
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/autoscaling Issues and PRs that pertain to the autoscaling service. stale Old or inactive issues managed by automation, if no further action taken these will get closed.

Comments

@ghost
Copy link

ghost commented Nov 6, 2018

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

@bflad bflad added enhancement Requests to existing resources that expand the functionality or scope. service/autoscaling Issues and PRs that pertain to the autoscaling service. labels Nov 6, 2018
@apparentlymart
Copy link
Contributor

This was held over in the core repository originally because there was no way to validate this at the time. Now that we have CustomizeDiff, which can serve as a validation mechanism, I sent this over here to see if you'd like to address it using that mechanism.

@github-actions
Copy link

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!

@github-actions github-actions bot added the stale Old or inactive issues managed by automation, if no further action taken these will get closed. label Oct 27, 2020
@jjshoe
Copy link

jjshoe commented Oct 30, 2020

bump

@ghost ghost removed the stale Old or inactive issues managed by automation, if no further action taken these will get closed. label Oct 30, 2020
@github-actions
Copy link

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!

@github-actions github-actions bot added the stale Old or inactive issues managed by automation, if no further action taken these will get closed. label Oct 20, 2022
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 20, 2022
@github-actions
Copy link

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.
If you have found a problem that seems similar to this, 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 Dec 21, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/autoscaling Issues and PRs that pertain to the autoscaling service. stale Old or inactive issues managed by automation, if no further action taken these will get closed.
Projects
None yet
Development

No branches or pull requests

3 participants