Open romanini-ciandt opened 5 months ago
Without having taken a very close look, this might be an easy fix: https://github.com/GoogleCloudPlatform/magic-modules/blob/main/mmv1/products/kms/KeyRingImportJob.yaml#L70-L78
We'll have to check the tests and if anything else needs to be changed though
Note from triage: Actual list of values that should be supported: https://cloud.google.com/kms/docs/reference/rest/v1/projects.locations.keyRings.importJobs#importmethod
If this field is expected to change frequently, it could make sense to eliminate the validation of enum values altogether so the provider doesn't have to be updated each time.
Community Note
Description
Comparing google_kms_key_ring_import_job terraform resource with keyring import-jobs API it is possible to notice that specifically for
import_method
field:RSA_OAEP_3072_SHA1_AES_256
,RSA_OAEP_4096_SHA1_AES_256
.rsa-oaep-3072-sha1-aes-256
,rsa-oaep-3072-sha256
,rsa-oaep-3072-sha256-aes-256
,rsa-oaep-4096-sha1-aes-256
,rsa-oaep-4096-sha256
,rsa-oaep-4096-sha256-aes-256
.For the use case I'm building a terraform automation, I have the explicit requirement to use
rsa-oaep-4096-sha256
and because it is not available I won't be able to achieve the expected result by usinggoogle_kms_key_ring_import_job
resource. I'll need to usegcloud
instead.New or Affected Resource(s)
Potential Terraform Configuration
References
No response
b/328081938