You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
Please do not leave +1 or me too comments, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
If an issue is assigned to the 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 to hashibot, a community member has claimed the issue already.
Terraform Version
Terraform v1.1.7
on linux_amd64
+ provider registry.terraform.io/hashicorp/google v4.15.0
The imported google_kms_crypto_key ID should be the same as the created one.
Actual Behavior
The imported google_kms_crypto_key ID has changed from projects/<gcp_project_id>/locations/europe/keyRings/my-key-ring/cryptoKeys/my-key" to <gcp_project_id>/europe/my-key-ring/my-key.
This will trigger an invalid amdement of google_storage_bucket or google_bigquery_dataset if default_encryption_configuration sets to the imported crypto key.
The text was updated successfully, but these errors were encountered:
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.
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
Expected Behavior
The imported
google_kms_crypto_key
ID should be the same as the created one.Actual Behavior
The imported
google_kms_crypto_key
ID has changed fromprojects/<gcp_project_id>/locations/europe/keyRings/my-key-ring/cryptoKeys/my-key"
to<gcp_project_id>/europe/my-key-ring/my-key
.Steps to Reproduce
terraform apply
terraform state show google_kms_crypto_key.my-key
terraform state rm google_kms_crypto_key.my-key
terraform import 'google_kms_crypto_key.my-key' <gcp_project_id>/europe/my-key-ring/my-key
terraform state show google_kms_crypto_key.my-key
Important Factoids
This will trigger an invalid amdement of
google_storage_bucket
orgoogle_bigquery_dataset
ifdefault_encryption_configuration
sets to the imported crypto key.The text was updated successfully, but these errors were encountered: