pulumi-gcp 7.0.0rc0__py3-none-any.whl → 7.1.0__py3-none-any.whl

pulumi_gcp/kms/crypto_key.py

@@ -214,8 +214,7 @@ class _CryptoKeyState:
         Input properties used for looking up and filtering CryptoKey resources.
         :param pulumi.Input[str] destroy_scheduled_duration: The period of time that versions of this key spend in the DESTROY_SCHEDULED state before transitioning to DESTROYED.
                If not specified at creation time, the default duration is 24 hours.
-        :param pulumi.Input[Mapping[str, pulumi.Input[str]]] effective_labels: All of labels (key/value pairs) present on the resource in GCP, including the labels configured through Terraform, other
-               clients and services.
+        :param pulumi.Input[Mapping[str, pulumi.Input[str]]] effective_labels: All of labels (key/value pairs) present on the resource in GCP, including the labels configured through Pulumi, other clients and services.
         :param pulumi.Input[bool] import_only: Whether this key may contain imported versions only.
         :param pulumi.Input[str] key_ring: The KeyRing that this key belongs to.
                Format: `'projects/{{project}}/locations/{{location}}/keyRings/{{keyRing}}'`.
@@ -282,8 +281,7 @@ class _CryptoKeyState:
     @pulumi.getter(name="effectiveLabels")
     def effective_labels(self) -> Optional[pulumi.Input[Mapping[str, pulumi.Input[str]]]]:
         """
-        All of labels (key/value pairs) present on the resource in GCP, including the labels configured through Terraform, other
-        clients and services.
+        All of labels (key/value pairs) present on the resource in GCP, including the labels configured through Pulumi, other clients and services.
         """
         return pulumi.get(self, "effective_labels")
 
@@ -477,7 +475,15 @@ class CryptoKey(pulumi.CustomResource):
 
         ## Import
 
-        CryptoKey can be imported using any of these accepted formats
+        CryptoKey can be imported using any of these accepted formats* `{{key_ring}}/cryptoKeys/{{name}}` * `{{key_ring}}/{{name}}` In Terraform v1.5.0 and later, use an [`import` block](https://developer.hashicorp.com/terraform/language/import) to import CryptoKey using one of the formats above. For exampletf import {
+
+         id = "{{key_ring}}/cryptoKeys/{{name}}"
+
+         to = google_kms_crypto_key.default }
+
+        ```sh
+         $ pulumi import gcp:kms/cryptoKey:CryptoKey When using the [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import), CryptoKey can be imported using one of the formats above. For example
+        ```
 
         ```sh
          $ pulumi import gcp:kms/cryptoKey:CryptoKey default {{key_ring}}/cryptoKeys/{{name}}
@@ -567,7 +573,15 @@ class CryptoKey(pulumi.CustomResource):
 
         ## Import
 
-        CryptoKey can be imported using any of these accepted formats
+        CryptoKey can be imported using any of these accepted formats* `{{key_ring}}/cryptoKeys/{{name}}` * `{{key_ring}}/{{name}}` In Terraform v1.5.0 and later, use an [`import` block](https://developer.hashicorp.com/terraform/language/import) to import CryptoKey using one of the formats above. For exampletf import {
+
+         id = "{{key_ring}}/cryptoKeys/{{name}}"
+
+         to = google_kms_crypto_key.default }
+
+        ```sh
+         $ pulumi import gcp:kms/cryptoKey:CryptoKey When using the [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import), CryptoKey can be imported using one of the formats above. For example
+        ```
 
         ```sh
          $ pulumi import gcp:kms/cryptoKey:CryptoKey default {{key_ring}}/cryptoKeys/{{name}}
@@ -655,8 +669,7 @@ class CryptoKey(pulumi.CustomResource):
         :param pulumi.ResourceOptions opts: Options for the resource.
         :param pulumi.Input[str] destroy_scheduled_duration: The period of time that versions of this key spend in the DESTROY_SCHEDULED state before transitioning to DESTROYED.
                If not specified at creation time, the default duration is 24 hours.
-        :param pulumi.Input[Mapping[str, pulumi.Input[str]]] effective_labels: All of labels (key/value pairs) present on the resource in GCP, including the labels configured through Terraform, other
-               clients and services.
+        :param pulumi.Input[Mapping[str, pulumi.Input[str]]] effective_labels: All of labels (key/value pairs) present on the resource in GCP, including the labels configured through Pulumi, other clients and services.
         :param pulumi.Input[bool] import_only: Whether this key may contain imported versions only.
         :param pulumi.Input[str] key_ring: The KeyRing that this key belongs to.
                Format: `'projects/{{project}}/locations/{{location}}/keyRings/{{keyRing}}'`.
@@ -713,8 +726,7 @@ class CryptoKey(pulumi.CustomResource):
     @pulumi.getter(name="effectiveLabels")
     def effective_labels(self) -> pulumi.Output[Mapping[str, str]]:
         """
-        All of labels (key/value pairs) present on the resource in GCP, including the labels configured through Terraform, other
-        clients and services.
+        All of labels (key/value pairs) present on the resource in GCP, including the labels configured through Pulumi, other clients and services.
         """
         return pulumi.get(self, "effective_labels")
 

pulumi_gcp/kms/crypto_key_iam_binding.py

@@ -329,28 +329,18 @@ class CryptoKeyIAMBinding(pulumi.CustomResource):
 
         ## Import
 
-        IAM member imports use space-delimited identifiers; the resource in question, the role, and the account.
+        ### Importing IAM policies IAM policy imports use the identifier of the KMS crypto key only. For example* `{{project_id}}/{{location}}/{{key_ring_name}}/{{crypto_key_name}}` An [`import` block](https://developer.hashicorp.com/terraform/language/import) (Terraform v1.5.0 and later) can be used to import IAM policiestf import {
 
-        This member resource can be imported using the `crypto_key_id`, role, and member identity e.g.
+         id = "{{project_id}}/{{location}}/{{key_ring_name}}/{{crypto_key_name}}"
 
-        ```sh
-         $ pulumi import gcp:kms/cryptoKeyIAMBinding:CryptoKeyIAMBinding crypto_key "your-project-id/location-name/key-ring-name/key-name roles/viewer user:foo@example.com"
-        ```
-
-         IAM binding imports use space-delimited identifiers; first the resource in question and then the role.
-
-        These bindings can be imported using the `crypto_key_id` and role, e.g.
+         to = google_kms_crypto_key_iam_policy.default }
 
         ```sh
-         $ pulumi import gcp:kms/cryptoKeyIAMBinding:CryptoKeyIAMBinding crypto_key "your-project-id/location-name/key-ring-name/key-name roles/editor"
+         $ pulumi import gcp:kms/cryptoKeyIAMBinding:CryptoKeyIAMBinding The [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import) can also be used
         ```
 
-         IAM policy imports use the identifier of the resource in question.
-
-        This policy resource can be imported using the `crypto_key_id`, e.g.
-
         ```sh
-         $ pulumi import gcp:kms/cryptoKeyIAMBinding:CryptoKeyIAMBinding crypto_key your-project-id/location-name/key-ring-name/key-name
+         $ pulumi import gcp:kms/cryptoKeyIAMBinding:CryptoKeyIAMBinding default {{project_id}}/{{location}}/{{key_ring_name}}/{{crypto_key_name}}
         ```
 
         :param str resource_name: The name of the resource.
@@ -480,28 +470,18 @@ class CryptoKeyIAMBinding(pulumi.CustomResource):
 
         ## Import
 
-        IAM member imports use space-delimited identifiers; the resource in question, the role, and the account.
+        ### Importing IAM policies IAM policy imports use the identifier of the KMS crypto key only. For example* `{{project_id}}/{{location}}/{{key_ring_name}}/{{crypto_key_name}}` An [`import` block](https://developer.hashicorp.com/terraform/language/import) (Terraform v1.5.0 and later) can be used to import IAM policiestf import {
 
-        This member resource can be imported using the `crypto_key_id`, role, and member identity e.g.
+         id = "{{project_id}}/{{location}}/{{key_ring_name}}/{{crypto_key_name}}"
 
-        ```sh
-         $ pulumi import gcp:kms/cryptoKeyIAMBinding:CryptoKeyIAMBinding crypto_key "your-project-id/location-name/key-ring-name/key-name roles/viewer user:foo@example.com"
-        ```
-
-         IAM binding imports use space-delimited identifiers; first the resource in question and then the role.
-
-        These bindings can be imported using the `crypto_key_id` and role, e.g.
+         to = google_kms_crypto_key_iam_policy.default }
 
         ```sh
-         $ pulumi import gcp:kms/cryptoKeyIAMBinding:CryptoKeyIAMBinding crypto_key "your-project-id/location-name/key-ring-name/key-name roles/editor"
+         $ pulumi import gcp:kms/cryptoKeyIAMBinding:CryptoKeyIAMBinding The [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import) can also be used
         ```
 
-         IAM policy imports use the identifier of the resource in question.
-
-        This policy resource can be imported using the `crypto_key_id`, e.g.
-
         ```sh
-         $ pulumi import gcp:kms/cryptoKeyIAMBinding:CryptoKeyIAMBinding crypto_key your-project-id/location-name/key-ring-name/key-name
+         $ pulumi import gcp:kms/cryptoKeyIAMBinding:CryptoKeyIAMBinding default {{project_id}}/{{location}}/{{key_ring_name}}/{{crypto_key_name}}
         ```
 
         :param str resource_name: The name of the resource.

pulumi_gcp/kms/crypto_key_iam_member.py

@@ -329,28 +329,18 @@ class CryptoKeyIAMMember(pulumi.CustomResource):
 
         ## Import
 
-        IAM member imports use space-delimited identifiers; the resource in question, the role, and the account.
+        ### Importing IAM policies IAM policy imports use the identifier of the KMS crypto key only. For example* `{{project_id}}/{{location}}/{{key_ring_name}}/{{crypto_key_name}}` An [`import` block](https://developer.hashicorp.com/terraform/language/import) (Terraform v1.5.0 and later) can be used to import IAM policiestf import {
 
-        This member resource can be imported using the `crypto_key_id`, role, and member identity e.g.
+         id = "{{project_id}}/{{location}}/{{key_ring_name}}/{{crypto_key_name}}"
 
-        ```sh
-         $ pulumi import gcp:kms/cryptoKeyIAMMember:CryptoKeyIAMMember crypto_key "your-project-id/location-name/key-ring-name/key-name roles/viewer user:foo@example.com"
-        ```
-
-         IAM binding imports use space-delimited identifiers; first the resource in question and then the role.
-
-        These bindings can be imported using the `crypto_key_id` and role, e.g.
+         to = google_kms_crypto_key_iam_policy.default }
 
         ```sh
-         $ pulumi import gcp:kms/cryptoKeyIAMMember:CryptoKeyIAMMember crypto_key "your-project-id/location-name/key-ring-name/key-name roles/editor"
+         $ pulumi import gcp:kms/cryptoKeyIAMMember:CryptoKeyIAMMember The [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import) can also be used
         ```
 
-         IAM policy imports use the identifier of the resource in question.
-
-        This policy resource can be imported using the `crypto_key_id`, e.g.
-
         ```sh
-         $ pulumi import gcp:kms/cryptoKeyIAMMember:CryptoKeyIAMMember crypto_key your-project-id/location-name/key-ring-name/key-name
+         $ pulumi import gcp:kms/cryptoKeyIAMMember:CryptoKeyIAMMember default {{project_id}}/{{location}}/{{key_ring_name}}/{{crypto_key_name}}
         ```
 
         :param str resource_name: The name of the resource.
@@ -480,28 +470,18 @@ class CryptoKeyIAMMember(pulumi.CustomResource):
 
         ## Import
 
-        IAM member imports use space-delimited identifiers; the resource in question, the role, and the account.
+        ### Importing IAM policies IAM policy imports use the identifier of the KMS crypto key only. For example* `{{project_id}}/{{location}}/{{key_ring_name}}/{{crypto_key_name}}` An [`import` block](https://developer.hashicorp.com/terraform/language/import) (Terraform v1.5.0 and later) can be used to import IAM policiestf import {
 
-        This member resource can be imported using the `crypto_key_id`, role, and member identity e.g.
+         id = "{{project_id}}/{{location}}/{{key_ring_name}}/{{crypto_key_name}}"
 
-        ```sh
-         $ pulumi import gcp:kms/cryptoKeyIAMMember:CryptoKeyIAMMember crypto_key "your-project-id/location-name/key-ring-name/key-name roles/viewer user:foo@example.com"
-        ```
-
-         IAM binding imports use space-delimited identifiers; first the resource in question and then the role.
-
-        These bindings can be imported using the `crypto_key_id` and role, e.g.
+         to = google_kms_crypto_key_iam_policy.default }
 
         ```sh
-         $ pulumi import gcp:kms/cryptoKeyIAMMember:CryptoKeyIAMMember crypto_key "your-project-id/location-name/key-ring-name/key-name roles/editor"
+         $ pulumi import gcp:kms/cryptoKeyIAMMember:CryptoKeyIAMMember The [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import) can also be used
         ```
 
-         IAM policy imports use the identifier of the resource in question.
-
-        This policy resource can be imported using the `crypto_key_id`, e.g.
-
         ```sh
-         $ pulumi import gcp:kms/cryptoKeyIAMMember:CryptoKeyIAMMember crypto_key your-project-id/location-name/key-ring-name/key-name
+         $ pulumi import gcp:kms/cryptoKeyIAMMember:CryptoKeyIAMMember default {{project_id}}/{{location}}/{{key_ring_name}}/{{crypto_key_name}}
         ```
 
         :param str resource_name: The name of the resource.

pulumi_gcp/kms/crypto_key_iam_policy.py

@@ -266,28 +266,18 @@ class CryptoKeyIAMPolicy(pulumi.CustomResource):
 
         ## Import
 
-        IAM member imports use space-delimited identifiers; the resource in question, the role, and the account.
+        ### Importing IAM policies IAM policy imports use the identifier of the KMS crypto key only. For example* `{{project_id}}/{{location}}/{{key_ring_name}}/{{crypto_key_name}}` An [`import` block](https://developer.hashicorp.com/terraform/language/import) (Terraform v1.5.0 and later) can be used to import IAM policiestf import {
 
-        This member resource can be imported using the `crypto_key_id`, role, and member identity e.g.
+         id = "{{project_id}}/{{location}}/{{key_ring_name}}/{{crypto_key_name}}"
 
-        ```sh
-         $ pulumi import gcp:kms/cryptoKeyIAMPolicy:CryptoKeyIAMPolicy crypto_key "your-project-id/location-name/key-ring-name/key-name roles/viewer user:foo@example.com"
-        ```
-
-         IAM binding imports use space-delimited identifiers; first the resource in question and then the role.
-
-        These bindings can be imported using the `crypto_key_id` and role, e.g.
+         to = google_kms_crypto_key_iam_policy.default }
 
         ```sh
-         $ pulumi import gcp:kms/cryptoKeyIAMPolicy:CryptoKeyIAMPolicy crypto_key "your-project-id/location-name/key-ring-name/key-name roles/editor"
+         $ pulumi import gcp:kms/cryptoKeyIAMPolicy:CryptoKeyIAMPolicy The [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import) can also be used
         ```
 
-         IAM policy imports use the identifier of the resource in question.
-
-        This policy resource can be imported using the `crypto_key_id`, e.g.
-
         ```sh
-         $ pulumi import gcp:kms/cryptoKeyIAMPolicy:CryptoKeyIAMPolicy crypto_key your-project-id/location-name/key-ring-name/key-name
+         $ pulumi import gcp:kms/cryptoKeyIAMPolicy:CryptoKeyIAMPolicy default {{project_id}}/{{location}}/{{key_ring_name}}/{{crypto_key_name}}
         ```
 
         :param str resource_name: The name of the resource.
@@ -415,28 +405,18 @@ class CryptoKeyIAMPolicy(pulumi.CustomResource):
 
         ## Import
 
-        IAM member imports use space-delimited identifiers; the resource in question, the role, and the account.
+        ### Importing IAM policies IAM policy imports use the identifier of the KMS crypto key only. For example* `{{project_id}}/{{location}}/{{key_ring_name}}/{{crypto_key_name}}` An [`import` block](https://developer.hashicorp.com/terraform/language/import) (Terraform v1.5.0 and later) can be used to import IAM policiestf import {
 
-        This member resource can be imported using the `crypto_key_id`, role, and member identity e.g.
+         id = "{{project_id}}/{{location}}/{{key_ring_name}}/{{crypto_key_name}}"
 
-        ```sh
-         $ pulumi import gcp:kms/cryptoKeyIAMPolicy:CryptoKeyIAMPolicy crypto_key "your-project-id/location-name/key-ring-name/key-name roles/viewer user:foo@example.com"
-        ```
-
-         IAM binding imports use space-delimited identifiers; first the resource in question and then the role.
-
-        These bindings can be imported using the `crypto_key_id` and role, e.g.
+         to = google_kms_crypto_key_iam_policy.default }
 
         ```sh
-         $ pulumi import gcp:kms/cryptoKeyIAMPolicy:CryptoKeyIAMPolicy crypto_key "your-project-id/location-name/key-ring-name/key-name roles/editor"
+         $ pulumi import gcp:kms/cryptoKeyIAMPolicy:CryptoKeyIAMPolicy The [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import) can also be used
         ```
 
-         IAM policy imports use the identifier of the resource in question.
-
-        This policy resource can be imported using the `crypto_key_id`, e.g.
-
         ```sh
-         $ pulumi import gcp:kms/cryptoKeyIAMPolicy:CryptoKeyIAMPolicy crypto_key your-project-id/location-name/key-ring-name/key-name
+         $ pulumi import gcp:kms/cryptoKeyIAMPolicy:CryptoKeyIAMPolicy default {{project_id}}/{{location}}/{{key_ring_name}}/{{crypto_key_name}}
         ```
 
         :param str resource_name: The name of the resource.

pulumi_gcp/kms/crypto_key_version.py

@@ -231,7 +231,15 @@ class CryptoKeyVersion(pulumi.CustomResource):
 
         ## Import
 
-        CryptoKeyVersion can be imported using any of these accepted formats:
+        CryptoKeyVersion can be imported using any of these accepted formats* `{{name}}` In Terraform v1.5.0 and later, use an [`import` block](https://developer.hashicorp.com/terraform/language/import) to import CryptoKeyVersion using one of the formats above. For exampletf import {
+
+         id = "{{name}}"
+
+         to = google_kms_crypto_key_version.default }
+
+        ```sh
+         $ pulumi import gcp:kms/cryptoKeyVersion:CryptoKeyVersion When using the [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import), CryptoKeyVersion can be imported using one of the formats above. For example
+        ```
 
         ```sh
          $ pulumi import gcp:kms/cryptoKeyVersion:CryptoKeyVersion default {{name}}
@@ -280,7 +288,15 @@ class CryptoKeyVersion(pulumi.CustomResource):
 
         ## Import
 
-        CryptoKeyVersion can be imported using any of these accepted formats:
+        CryptoKeyVersion can be imported using any of these accepted formats* `{{name}}` In Terraform v1.5.0 and later, use an [`import` block](https://developer.hashicorp.com/terraform/language/import) to import CryptoKeyVersion using one of the formats above. For exampletf import {
+
+         id = "{{name}}"
+
+         to = google_kms_crypto_key_version.default }
+
+        ```sh
+         $ pulumi import gcp:kms/cryptoKeyVersion:CryptoKeyVersion When using the [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import), CryptoKeyVersion can be imported using one of the formats above. For example
+        ```
 
         ```sh
          $ pulumi import gcp:kms/cryptoKeyVersion:CryptoKeyVersion default {{name}}

pulumi_gcp/kms/key_ring.py

@@ -176,7 +176,15 @@ class KeyRing(pulumi.CustomResource):
 
         ## Import
 
-        KeyRing can be imported using any of these accepted formats
+        KeyRing can be imported using any of these accepted formats* `projects/{{project}}/locations/{{location}}/keyRings/{{name}}` * `{{project}}/{{location}}/{{name}}` * `{{location}}/{{name}}` In Terraform v1.5.0 and later, use an [`import` block](https://developer.hashicorp.com/terraform/language/import) to import KeyRing using one of the formats above. For exampletf import {
+
+         id = "projects/{{project}}/locations/{{location}}/keyRings/{{name}}"
+
+         to = google_kms_key_ring.default }
+
+        ```sh
+         $ pulumi import gcp:kms/keyRing:KeyRing When using the [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import), KeyRing can be imported using one of the formats above. For example
+        ```
 
         ```sh
          $ pulumi import gcp:kms/keyRing:KeyRing default projects/{{project}}/locations/{{location}}/keyRings/{{name}}
@@ -232,7 +240,15 @@ class KeyRing(pulumi.CustomResource):
 
         ## Import
 
-        KeyRing can be imported using any of these accepted formats
+        KeyRing can be imported using any of these accepted formats* `projects/{{project}}/locations/{{location}}/keyRings/{{name}}` * `{{project}}/{{location}}/{{name}}` * `{{location}}/{{name}}` In Terraform v1.5.0 and later, use an [`import` block](https://developer.hashicorp.com/terraform/language/import) to import KeyRing using one of the formats above. For exampletf import {
+
+         id = "projects/{{project}}/locations/{{location}}/keyRings/{{name}}"
+
+         to = google_kms_key_ring.default }
+
+        ```sh
+         $ pulumi import gcp:kms/keyRing:KeyRing When using the [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import), KeyRing can be imported using one of the formats above. For example
+        ```
 
         ```sh
          $ pulumi import gcp:kms/keyRing:KeyRing default projects/{{project}}/locations/{{location}}/keyRings/{{name}}

pulumi_gcp/kms/key_ring_iam_binding.py

@@ -340,28 +340,18 @@ class KeyRingIAMBinding(pulumi.CustomResource):
 
         ## Import
 
-        IAM member imports use space-delimited identifiers; the resource in question, the role, and the account.
+        ### Importing IAM policies IAM policy imports use the identifier of the Cloud KMS key ring only. For example* `{{project_id}}/{{location}}/{{key_ring_name}}` An [`import` block](https://developer.hashicorp.com/terraform/language/import) (Terraform v1.5.0 and later) can be used to import IAM policiestf import {
 
-        This member resource can be imported using the `key_ring_id`, role, and account e.g.
+         id = "{{project_id}}/{{location}}/{{key_ring_name}}"
 
-        ```sh
-         $ pulumi import gcp:kms/keyRingIAMBinding:KeyRingIAMBinding key_ring_iam "your-project-id/location-name/key-ring-name roles/viewer user:foo@example.com"
-        ```
-
-         IAM binding imports use space-delimited identifiers; the resource in question and the role.
-
-        This binding resource can be imported using the `key_ring_id` and role, e.g.
+         to = google_kms_key_ring_iam_policy.default }
 
         ```sh
-         $ pulumi import gcp:kms/keyRingIAMBinding:KeyRingIAMBinding key_ring_iam "your-project-id/location-name/key-ring-name roles/cloudkms.admin"
+         $ pulumi import gcp:kms/keyRingIAMBinding:KeyRingIAMBinding The [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import) can also be used
         ```
 
-         IAM policy imports use the identifier of the resource in question.
-
-        This policy resource can be imported using the `key_ring_id`, e.g.
-
         ```sh
-         $ pulumi import gcp:kms/keyRingIAMBinding:KeyRingIAMBinding key_ring_iam your-project-id/location-name/key-ring-name
+         $ pulumi import gcp:kms/keyRingIAMBinding:KeyRingIAMBinding default {{project_id}}/{{location}}/{{key_ring_name}}
         ```
 
         :param str resource_name: The name of the resource.
@@ -499,28 +489,18 @@ class KeyRingIAMBinding(pulumi.CustomResource):
 
         ## Import
 
-        IAM member imports use space-delimited identifiers; the resource in question, the role, and the account.
+        ### Importing IAM policies IAM policy imports use the identifier of the Cloud KMS key ring only. For example* `{{project_id}}/{{location}}/{{key_ring_name}}` An [`import` block](https://developer.hashicorp.com/terraform/language/import) (Terraform v1.5.0 and later) can be used to import IAM policiestf import {
 
-        This member resource can be imported using the `key_ring_id`, role, and account e.g.
+         id = "{{project_id}}/{{location}}/{{key_ring_name}}"
 
-        ```sh
-         $ pulumi import gcp:kms/keyRingIAMBinding:KeyRingIAMBinding key_ring_iam "your-project-id/location-name/key-ring-name roles/viewer user:foo@example.com"
-        ```
-
-         IAM binding imports use space-delimited identifiers; the resource in question and the role.
-
-        This binding resource can be imported using the `key_ring_id` and role, e.g.
+         to = google_kms_key_ring_iam_policy.default }
 
         ```sh
-         $ pulumi import gcp:kms/keyRingIAMBinding:KeyRingIAMBinding key_ring_iam "your-project-id/location-name/key-ring-name roles/cloudkms.admin"
+         $ pulumi import gcp:kms/keyRingIAMBinding:KeyRingIAMBinding The [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import) can also be used
         ```
 
-         IAM policy imports use the identifier of the resource in question.
-
-        This policy resource can be imported using the `key_ring_id`, e.g.
-
         ```sh
-         $ pulumi import gcp:kms/keyRingIAMBinding:KeyRingIAMBinding key_ring_iam your-project-id/location-name/key-ring-name
+         $ pulumi import gcp:kms/keyRingIAMBinding:KeyRingIAMBinding default {{project_id}}/{{location}}/{{key_ring_name}}
         ```
 
         :param str resource_name: The name of the resource.

pulumi_gcp/kms/key_ring_iam_member.py

@@ -340,28 +340,18 @@ class KeyRingIAMMember(pulumi.CustomResource):
 
         ## Import
 
-        IAM member imports use space-delimited identifiers; the resource in question, the role, and the account.
+        ### Importing IAM policies IAM policy imports use the identifier of the Cloud KMS key ring only. For example* `{{project_id}}/{{location}}/{{key_ring_name}}` An [`import` block](https://developer.hashicorp.com/terraform/language/import) (Terraform v1.5.0 and later) can be used to import IAM policiestf import {
 
-        This member resource can be imported using the `key_ring_id`, role, and account e.g.
+         id = "{{project_id}}/{{location}}/{{key_ring_name}}"
 
-        ```sh
-         $ pulumi import gcp:kms/keyRingIAMMember:KeyRingIAMMember key_ring_iam "your-project-id/location-name/key-ring-name roles/viewer user:foo@example.com"
-        ```
-
-         IAM binding imports use space-delimited identifiers; the resource in question and the role.
-
-        This binding resource can be imported using the `key_ring_id` and role, e.g.
+         to = google_kms_key_ring_iam_policy.default }
 
         ```sh
-         $ pulumi import gcp:kms/keyRingIAMMember:KeyRingIAMMember key_ring_iam "your-project-id/location-name/key-ring-name roles/cloudkms.admin"
+         $ pulumi import gcp:kms/keyRingIAMMember:KeyRingIAMMember The [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import) can also be used
         ```
 
-         IAM policy imports use the identifier of the resource in question.
-
-        This policy resource can be imported using the `key_ring_id`, e.g.
-
         ```sh
-         $ pulumi import gcp:kms/keyRingIAMMember:KeyRingIAMMember key_ring_iam your-project-id/location-name/key-ring-name
+         $ pulumi import gcp:kms/keyRingIAMMember:KeyRingIAMMember default {{project_id}}/{{location}}/{{key_ring_name}}
         ```
 
         :param str resource_name: The name of the resource.
@@ -499,28 +489,18 @@ class KeyRingIAMMember(pulumi.CustomResource):
 
         ## Import
 
-        IAM member imports use space-delimited identifiers; the resource in question, the role, and the account.
+        ### Importing IAM policies IAM policy imports use the identifier of the Cloud KMS key ring only. For example* `{{project_id}}/{{location}}/{{key_ring_name}}` An [`import` block](https://developer.hashicorp.com/terraform/language/import) (Terraform v1.5.0 and later) can be used to import IAM policiestf import {
 
-        This member resource can be imported using the `key_ring_id`, role, and account e.g.
+         id = "{{project_id}}/{{location}}/{{key_ring_name}}"
 
-        ```sh
-         $ pulumi import gcp:kms/keyRingIAMMember:KeyRingIAMMember key_ring_iam "your-project-id/location-name/key-ring-name roles/viewer user:foo@example.com"
-        ```
-
-         IAM binding imports use space-delimited identifiers; the resource in question and the role.
-
-        This binding resource can be imported using the `key_ring_id` and role, e.g.
+         to = google_kms_key_ring_iam_policy.default }
 
         ```sh
-         $ pulumi import gcp:kms/keyRingIAMMember:KeyRingIAMMember key_ring_iam "your-project-id/location-name/key-ring-name roles/cloudkms.admin"
+         $ pulumi import gcp:kms/keyRingIAMMember:KeyRingIAMMember The [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import) can also be used
         ```
 
-         IAM policy imports use the identifier of the resource in question.
-
-        This policy resource can be imported using the `key_ring_id`, e.g.
-
         ```sh
-         $ pulumi import gcp:kms/keyRingIAMMember:KeyRingIAMMember key_ring_iam your-project-id/location-name/key-ring-name
+         $ pulumi import gcp:kms/keyRingIAMMember:KeyRingIAMMember default {{project_id}}/{{location}}/{{key_ring_name}}
         ```
 
         :param str resource_name: The name of the resource.

pulumi_gcp/kms/key_ring_iam_policy.py

@@ -273,28 +273,18 @@ class KeyRingIAMPolicy(pulumi.CustomResource):
 
         ## Import
 
-        IAM member imports use space-delimited identifiers; the resource in question, the role, and the account.
+        ### Importing IAM policies IAM policy imports use the identifier of the Cloud KMS key ring only. For example* `{{project_id}}/{{location}}/{{key_ring_name}}` An [`import` block](https://developer.hashicorp.com/terraform/language/import) (Terraform v1.5.0 and later) can be used to import IAM policiestf import {
 
-        This member resource can be imported using the `key_ring_id`, role, and account e.g.
+         id = "{{project_id}}/{{location}}/{{key_ring_name}}"
 
-        ```sh
-         $ pulumi import gcp:kms/keyRingIAMPolicy:KeyRingIAMPolicy key_ring_iam "your-project-id/location-name/key-ring-name roles/viewer user:foo@example.com"
-        ```
-
-         IAM binding imports use space-delimited identifiers; the resource in question and the role.
-
-        This binding resource can be imported using the `key_ring_id` and role, e.g.
+         to = google_kms_key_ring_iam_policy.default }
 
         ```sh
-         $ pulumi import gcp:kms/keyRingIAMPolicy:KeyRingIAMPolicy key_ring_iam "your-project-id/location-name/key-ring-name roles/cloudkms.admin"
+         $ pulumi import gcp:kms/keyRingIAMPolicy:KeyRingIAMPolicy The [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import) can also be used
         ```
 
-         IAM policy imports use the identifier of the resource in question.
-
-        This policy resource can be imported using the `key_ring_id`, e.g.
-
         ```sh
-         $ pulumi import gcp:kms/keyRingIAMPolicy:KeyRingIAMPolicy key_ring_iam your-project-id/location-name/key-ring-name
+         $ pulumi import gcp:kms/keyRingIAMPolicy:KeyRingIAMPolicy default {{project_id}}/{{location}}/{{key_ring_name}}
         ```
 
         :param str resource_name: The name of the resource.
@@ -429,28 +419,18 @@ class KeyRingIAMPolicy(pulumi.CustomResource):
 
         ## Import
 
-        IAM member imports use space-delimited identifiers; the resource in question, the role, and the account.
+        ### Importing IAM policies IAM policy imports use the identifier of the Cloud KMS key ring only. For example* `{{project_id}}/{{location}}/{{key_ring_name}}` An [`import` block](https://developer.hashicorp.com/terraform/language/import) (Terraform v1.5.0 and later) can be used to import IAM policiestf import {
 
-        This member resource can be imported using the `key_ring_id`, role, and account e.g.
+         id = "{{project_id}}/{{location}}/{{key_ring_name}}"
 
-        ```sh
-         $ pulumi import gcp:kms/keyRingIAMPolicy:KeyRingIAMPolicy key_ring_iam "your-project-id/location-name/key-ring-name roles/viewer user:foo@example.com"
-        ```
-
-         IAM binding imports use space-delimited identifiers; the resource in question and the role.
-
-        This binding resource can be imported using the `key_ring_id` and role, e.g.
+         to = google_kms_key_ring_iam_policy.default }
 
         ```sh
-         $ pulumi import gcp:kms/keyRingIAMPolicy:KeyRingIAMPolicy key_ring_iam "your-project-id/location-name/key-ring-name roles/cloudkms.admin"
+         $ pulumi import gcp:kms/keyRingIAMPolicy:KeyRingIAMPolicy The [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import) can also be used
         ```
 
-         IAM policy imports use the identifier of the resource in question.
-
-        This policy resource can be imported using the `key_ring_id`, e.g.
-
         ```sh
-         $ pulumi import gcp:kms/keyRingIAMPolicy:KeyRingIAMPolicy key_ring_iam your-project-id/location-name/key-ring-name
+         $ pulumi import gcp:kms/keyRingIAMPolicy:KeyRingIAMPolicy default {{project_id}}/{{location}}/{{key_ring_name}}
         ```
 
         :param str resource_name: The name of the resource.

pulumi_gcp/kms/key_ring_import_job.py

@@ -301,7 +301,15 @@ class KeyRingImportJob(pulumi.CustomResource):
 
         ## Import
 
-        KeyRingImportJob can be imported using any of these accepted formats:
+        KeyRingImportJob can be imported using any of these accepted formats* `{{name}}` In Terraform v1.5.0 and later, use an [`import` block](https://developer.hashicorp.com/terraform/language/import) to import KeyRingImportJob using one of the formats above. For exampletf import {
+
+         id = "{{name}}"
+
+         to = google_kms_key_ring_import_job.default }
+
+        ```sh
+         $ pulumi import gcp:kms/keyRingImportJob:KeyRingImportJob When using the [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import), KeyRingImportJob can be imported using one of the formats above. For example
+        ```
 
         ```sh
          $ pulumi import gcp:kms/keyRingImportJob:KeyRingImportJob default {{name}}
@@ -347,7 +355,15 @@ class KeyRingImportJob(pulumi.CustomResource):
 
         ## Import
 
-        KeyRingImportJob can be imported using any of these accepted formats:
+        KeyRingImportJob can be imported using any of these accepted formats* `{{name}}` In Terraform v1.5.0 and later, use an [`import` block](https://developer.hashicorp.com/terraform/language/import) to import KeyRingImportJob using one of the formats above. For exampletf import {
+
+         id = "{{name}}"
+
+         to = google_kms_key_ring_import_job.default }
+
+        ```sh
+         $ pulumi import gcp:kms/keyRingImportJob:KeyRingImportJob When using the [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import), KeyRingImportJob can be imported using one of the formats above. For example
+        ```
 
         ```sh
          $ pulumi import gcp:kms/keyRingImportJob:KeyRingImportJob default {{name}}