-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
using id instead of self_link field in google_kms_crypto_key broke the plan #10563
Comments
@hablislim there is below breaking change in v4.0.0. You may need to update your code accordingly. |
I'm seeing this issue as well. The problem seems ot be that the My configuration looks roughly like this:
This gives me this suggested change:
However, applying this change results in the following error:
|
In my case when I tried self_link and id I noticed the same format and my plan got applied. |
Experiencing the same issue with Have to use the following workaround for now:
|
Thank you @djfinnoy |
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
modular-magician
user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned tohashibot
, a community member has claimed the issue already.Terraform Version
Affected Resource(s)
Terraform Configuration Files
Debug Output
Panic Output
Expected Behavior
Changing self_link by id on google_kms_crypto_key when upgrading from 3.88.0 to 4.0.0, should return no changes
Actual Behavior
By running a terraform apply again , the change shows a new creation of the existing cluster
The whole terrafrom state was broken when running the plan again:
Steps to Reproduce
terraform apply
Important Factoids
NA
The text was updated successfully, but these errors were encountered: