Add cryptoKeyBackend field to KMS CryptoKey.

This is needed for EXTERNAL_VPC key creation.
tdbhacks · Mar 15, 2024 · 3988c67 · 3988c67
1 parent 917c875
commit 3988c67
Show file tree

Hide file tree

Showing 2 changed files with 10 additions and 0 deletions.
diff --git a/mmv1/products/kms/CryptoKey.yaml b/mmv1/products/kms/CryptoKey.yaml
@@ -156,3 +156,10 @@ properties:
     description: |
       Whether this key may contain imported versions only.
     default_from_api: true
+  - !ruby/object:Api::Type::String
+    name: 'cryptoKeyBackend'
+    immutable: true
+    description: |
+      The resource name of the backend environment associated with all CryptoKeyVersions within this CryptoKey.
+      The resource name is in the format "projects/*/locations/*/ekmConnections/*" and only applies to "EXTERNAL_VPC" keys.
+    default_from_api: true
diff --git a/mmv1/products/kms/CryptoKeyVersion.yaml b/mmv1/products/kms/CryptoKeyVersion.yaml
@@ -139,6 +139,9 @@ properties:
     name: 'externalProtectionLevelOptions'
     description: |
       ExternalProtectionLevelOptions stores a group of additional fields for configuring a CryptoKeyVersion that are specific to the EXTERNAL protection level and EXTERNAL_VPC protection levels.
+    update_mask_fields:
+      - 'externalProtectionLevelOptions.externalKeyUri'
+      - 'externalProtectionLevelOptions.ekmConnectionKeyPath'
     properties:
       - !ruby/object:Api::Type::String
         name: 'externalKeyUri'