-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
new AWS provider 3.35 can't set aws_ssm_parameter with tags and overwrite #18550
Comments
@djsuszi Thanks for raising this issue. Related: |
Ireland eu-west-1 |
I'm seeing the same issue with 3.35, fixed with locking to 3.34. us-gov-west-1 region |
We are seeing the same thing as well |
Same here with 3.35. Fixed using 3.34.0 |
Same issue with v3.35 here:
|
I +1 the submission but wanted to call out that I am seeing this in us-east-1. |
This has also broken my deployments as all my ssm_parameter resources have tags set and overwrite=true. |
I've also had to roll back to version 3.34.0 due to this breaking all our pipelines. It seems that even after setting overwrite to false and creating the resource is not idempotent and wants to add the tags the second terraform plan run fails because overwrite is set to false.
|
This has been released in version 3.36.0 of the Terraform AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template for triage. Thanks! |
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
Plan:
is giving error:
when I force old provider (version = "3.34") same code it's working fine
Terraform CLI and Terraform AWS Provider Version
terraform version: 0.12.29
hashicorp/aws 3.35.0
Affected Resource(s)
aws_ssm_parameter
Expected Behavior
it should work like in 3.34
Steps to Reproduce
try to use resource "aws_ssm_parameter" with overwrite and tags
The text was updated successfully, but these errors were encountered: