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

google_kms_crypto_key ID changed after importing #11366

Closed
blakey22 opened this issue Mar 29, 2022 · 2 comments
Closed

google_kms_crypto_key ID changed after importing #11366

blakey22 opened this issue Mar 29, 2022 · 2 comments
Labels

Comments

@blakey22
Copy link

Community Note

  • 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

Affected Resource(s)

  • google_kms_crypto_key

Terraform Configuration Files

resource "google_kms_key_ring" "my-key-ring" {
  project  = "<gcp_project_id>"
  name     = "my-key-ring"
  location = "europe"
}

resource "google_kms_crypto_key" "my-key" {
  name     = "my-key"
  key_ring = google_kms_key_ring.my-key-ring.id
}

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 from projects/<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

  1. terraform apply
  2. terraform state show google_kms_crypto_key.my-key
  3. terraform state rm google_kms_crypto_key.my-key
  4. terraform import 'google_kms_crypto_key.my-key' <gcp_project_id>/europe/my-key-ring/my-key
  5. terraform state show google_kms_crypto_key.my-key

Important Factoids

This will trigger an invalid amdement of google_storage_bucket or google_bigquery_dataset if default_encryption_configuration sets to the imported crypto key.

@blakey22 blakey22 added the bug label Mar 29, 2022
@ScottSuarez
Copy link
Collaborator

@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 Apr 29, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants