-
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
KMS doesn't work with newest verision of provider #20588
Comments
I have this issue too. AWS provider version 3.54.0, Terraform version 1.0.4 |
Can you look into this? |
tested with newest provider. Still facing the same issue. Provider ver. 3.55 |
Am also having this issue. Need to test if the problem resolves with 3.49. Will report back. |
I can confirm the same problem. Terraform CLI version: 1.0.5 Tested down to version 3.52, and this is the latest version which is working fine and as expected.
Base TF is simple:
|
Didn't have to go back to 3.49 because using 3.52 resolves the issue. When looking at the release notes for 3.53 there was some functionality added to the aws_kms_key resource. When I tested 3.53 it fails on KMS creation with the same error(s) as 3.55 (current as of this writing). Functionality added to 3.53 (pasted from release notes) |
Adding to @dzandt 's experience: Had the same issue, also works fine with 3.52 |
It's still affecting hashicorp/aws v3.57.0 |
Also 3.58.0 is affected somehow in different combinations but not all the time. See test scenarios below: Working 1 (description only)
Working 2 (description AND tags)
Working 3 (description, enable_key_rotation, NO tags)
Working 4 (description, enable_key_rotation, policy, NO tags)
Not working 1 (description, enable_key_rotation and tags)
Not working 2 (description, enable_key_rotation, tags and policy):
|
rolling back to 3.52 also fixed the issue for me. |
This functionality has been released in v3.59.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. Thank you! |
I'm still seeing this error with 3.59.0. (Terraform 1.0.2).
|
I am also seeing the same.. I had to go back to 3.52 again. |
Can somebody tell us what is exactly "policy propagation", I don't see it documented anywhere... |
I'm also still seeing this error in 3.60 |
Still seeing this error in 3.61. Issue was:
Tried removing the second statement in the policy (leaving just the account lockout statement) and it created the key w/ policy. Tried making an update to the policy by adding second statement back but apply operation fails to complete successfully, same errors as above. |
yep, definitely still happening on 3.62 version of provider as well |
we should probably open new issue as this issue is closed and I doubt anybody is paying attention to the chat in closed issues |
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. |
Community Note
Terraform CLI and Terraform AWS Provider Version
0.14.7
Affected Resource(s)
Terraform Configuration Files
tested with below aws providers:
3.49 - works
3.53 - does not work
3.54 - does not work
Debug Output
Panic Output
Expected Behavior
Actual Behavior
Steps to Reproduce
terraform apply
Important Factoids
References
The text was updated successfully, but these errors were encountered: