-
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
add conditions to kms iam #2841
add conditions to kms iam #2841
Conversation
Hi! I'm the modular magician, I work on Magic Modules. Pull request statusesNo diff detected in terraform-google-conversion. New Pull RequestsI built this PR into one or more new PRs on other repositories, and when those are closed, this PR will also be merged and closed. |
Hi! I'm the modular magician, I work on Magic Modules. Pull request statusesterraform-provider-google-beta already has an open PR. New Pull RequestsI didn't open any new pull requests because of this PR. |
1 similar comment
Hi! I'm the modular magician, I work on Magic Modules. Pull request statusesterraform-provider-google-beta already has an open PR. New Pull RequestsI didn't open any new pull requests because of this PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense to not generate this at this point due to the parseKmsCryptoKeyId
usage
p, err := u.Config.clientKms.Projects.Locations.KeyRings.GetIamPolicy(u.resourceId).Do() | ||
<% else -%> | ||
p, err := u.Config.clientKms.Projects.Locations.KeyRings.GetIamPolicy(u.resourceId).OptionsRequestedPolicyVersion(iamPolicyVersion).Do() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we not need a similar change to the SetIamPolicy
calls? Maybe not because the policy would have the policy version attached by that point?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's already there in the resource_iam_*.go files
With IAM Conditions ([beta](https://terraform.io/docs/providers/google/provider_versions.html)): | ||
```hcl | ||
resource "google_kms_crypto_key_iam_member" "crypto_key" { | ||
crypto_key_id = "your-crypto-key-id" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Keep this consistent with the longer form?
crypto_key_id = "my-gcp-project/us-central1/my-key-ring/my-crypto-key"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated the docs to use more full examples that reference other resources instead of spelling out the ids
Hi! I'm the modular magician, I work on Magic Modules. Pull request statusesterraform-provider-google-beta already has an open PR. New Pull RequestsI didn't open any new pull requests because of this PR. |
Tracked submodules are build/terraform-beta build/terraform-mapper build/terraform build/ansible build/inspec.
0918780
to
682a04d
Compare
Part of hashicorp/terraform-provider-google#2909.
I opted not to generate these because the generated forms aren't compatible with the current forms- a generated cryptoKey iam resource for example would add a required field
key_ring_id
, and if we update thebase_url
so that thecrypto_key_id
represents the full self link, we would lose the import forms that we currently get.Release Note Template for Downstream PRs (will be copied)