pulumi-gcp 7.7.0a1706207981__py3-none-any.whl → 7.8.0__py3-none-any.whl

pulumi_gcp/logging/_inputs.py

@@ -43,7 +43,22 @@ class BillingAccountBucketConfigCmekSettingsArgs:
                  name: Optional[pulumi.Input[str]] = None,
                  service_account_id: Optional[pulumi.Input[str]] = None):
         """
+        :param pulumi.Input[str] kms_key_name: The resource name for the configured Cloud KMS key.
+               KMS key name format:
+               "projects/[PROJECT_ID]/locations/[LOCATION]/keyRings/[KEYRING]/cryptoKeys/[KEY]"
+               To enable CMEK for the bucket, set this field to a valid kmsKeyName for which the associated service account has the required cloudkms.cryptoKeyEncrypterDecrypter roles assigned for the key.
+               The Cloud KMS key used by the bucket can be updated by changing the kmsKeyName to a new valid key name. Encryption operations that are in progress will be completed with the key that was in use when they started. Decryption operations will be completed using the key that was used at the time of encryption unless access to that key has been revoked.
+               See [Enabling CMEK for Logging Buckets](https://cloud.google.com/logging/docs/routing/managed-encryption-storage) for more information.
+        :param pulumi.Input[str] kms_key_version_name: The CryptoKeyVersion resource name for the configured Cloud KMS key.
+               KMS key name format:
+               "projects/[PROJECT_ID]/locations/[LOCATION]/keyRings/[KEYRING]/cryptoKeys/[KEY]/cryptoKeyVersions/[VERSION]"
+               For example:
+               "projects/my-project/locations/us-central1/keyRings/my-ring/cryptoKeys/my-key/cryptoKeyVersions/1"
+               This is a read-only field used to convey the specific configured CryptoKeyVersion of kms_key that has been configured. It will be populated in cases where the CMEK settings are bound to a single key version.
         :param pulumi.Input[str] name: The resource name of the bucket. For example: "projects/my-project-id/locations/my-location/buckets/my-bucket-id"
+        :param pulumi.Input[str] service_account_id: The service account associated with a project for which CMEK will apply.
+               Before enabling CMEK for a logging bucket, you must first assign the cloudkms.cryptoKeyEncrypterDecrypter role to the service account associated with the project for which CMEK will apply. Use [v2.getCmekSettings](https://cloud.google.com/logging/docs/reference/v2/rest/v2/TopLevel/getCmekSettings#google.logging.v2.ConfigServiceV2.GetCmekSettings) to obtain the service account ID.
+               See [Enabling CMEK for Logging Buckets](https://cloud.google.com/logging/docs/routing/managed-encryption-storage) for more information.
         """
         pulumi.set(__self__, "kms_key_name", kms_key_name)
         if kms_key_version_name is not None:
@@ -56,6 +71,14 @@ class BillingAccountBucketConfigCmekSettingsArgs:
     @property
     @pulumi.getter(name="kmsKeyName")
     def kms_key_name(self) -> pulumi.Input[str]:
+        """
+        The resource name for the configured Cloud KMS key.
+        KMS key name format:
+        "projects/[PROJECT_ID]/locations/[LOCATION]/keyRings/[KEYRING]/cryptoKeys/[KEY]"
+        To enable CMEK for the bucket, set this field to a valid kmsKeyName for which the associated service account has the required cloudkms.cryptoKeyEncrypterDecrypter roles assigned for the key.
+        The Cloud KMS key used by the bucket can be updated by changing the kmsKeyName to a new valid key name. Encryption operations that are in progress will be completed with the key that was in use when they started. Decryption operations will be completed using the key that was used at the time of encryption unless access to that key has been revoked.
+        See [Enabling CMEK for Logging Buckets](https://cloud.google.com/logging/docs/routing/managed-encryption-storage) for more information.
+        """
         return pulumi.get(self, "kms_key_name")
 
     @kms_key_name.setter
@@ -65,6 +88,14 @@ class BillingAccountBucketConfigCmekSettingsArgs:
     @property
     @pulumi.getter(name="kmsKeyVersionName")
     def kms_key_version_name(self) -> Optional[pulumi.Input[str]]:
+        """
+        The CryptoKeyVersion resource name for the configured Cloud KMS key.
+        KMS key name format:
+        "projects/[PROJECT_ID]/locations/[LOCATION]/keyRings/[KEYRING]/cryptoKeys/[KEY]/cryptoKeyVersions/[VERSION]"
+        For example:
+        "projects/my-project/locations/us-central1/keyRings/my-ring/cryptoKeys/my-key/cryptoKeyVersions/1"
+        This is a read-only field used to convey the specific configured CryptoKeyVersion of kms_key that has been configured. It will be populated in cases where the CMEK settings are bound to a single key version.
+        """
         return pulumi.get(self, "kms_key_version_name")
 
     @kms_key_version_name.setter
@@ -86,6 +117,11 @@ class BillingAccountBucketConfigCmekSettingsArgs:
     @property
     @pulumi.getter(name="serviceAccountId")
     def service_account_id(self) -> Optional[pulumi.Input[str]]:
+        """
+        The service account associated with a project for which CMEK will apply.
+        Before enabling CMEK for a logging bucket, you must first assign the cloudkms.cryptoKeyEncrypterDecrypter role to the service account associated with the project for which CMEK will apply. Use [v2.getCmekSettings](https://cloud.google.com/logging/docs/reference/v2/rest/v2/TopLevel/getCmekSettings#google.logging.v2.ConfigServiceV2.GetCmekSettings) to obtain the service account ID.
+        See [Enabling CMEK for Logging Buckets](https://cloud.google.com/logging/docs/routing/managed-encryption-storage) for more information.
+        """
         return pulumi.get(self, "service_account_id")
 
     @service_account_id.setter
@@ -239,7 +275,22 @@ class FolderBucketConfigCmekSettingsArgs:
                  name: Optional[pulumi.Input[str]] = None,
                  service_account_id: Optional[pulumi.Input[str]] = None):
         """
+        :param pulumi.Input[str] kms_key_name: The resource name for the configured Cloud KMS key.
+               KMS key name format:
+               "projects/[PROJECT_ID]/locations/[LOCATION]/keyRings/[KEYRING]/cryptoKeys/[KEY]"
+               To enable CMEK for the bucket, set this field to a valid kmsKeyName for which the associated service account has the required cloudkms.cryptoKeyEncrypterDecrypter roles assigned for the key.
+               The Cloud KMS key used by the bucket can be updated by changing the kmsKeyName to a new valid key name. Encryption operations that are in progress will be completed with the key that was in use when they started. Decryption operations will be completed using the key that was used at the time of encryption unless access to that key has been revoked.
+               See [Enabling CMEK for Logging Buckets](https://cloud.google.com/logging/docs/routing/managed-encryption-storage) for more information.
+        :param pulumi.Input[str] kms_key_version_name: The CryptoKeyVersion resource name for the configured Cloud KMS key.
+               KMS key name format:
+               "projects/[PROJECT_ID]/locations/[LOCATION]/keyRings/[KEYRING]/cryptoKeys/[KEY]/cryptoKeyVersions/[VERSION]"
+               For example:
+               "projects/my-project/locations/us-central1/keyRings/my-ring/cryptoKeys/my-key/cryptoKeyVersions/1"
+               This is a read-only field used to convey the specific configured CryptoKeyVersion of kms_key that has been configured. It will be populated in cases where the CMEK settings are bound to a single key version.
         :param pulumi.Input[str] name: The resource name of the bucket. For example: "folders/my-folder-id/locations/my-location/buckets/my-bucket-id"
+        :param pulumi.Input[str] service_account_id: The service account associated with a project for which CMEK will apply.
+               Before enabling CMEK for a logging bucket, you must first assign the cloudkms.cryptoKeyEncrypterDecrypter role to the service account associated with the project for which CMEK will apply. Use [v2.getCmekSettings](https://cloud.google.com/logging/docs/reference/v2/rest/v2/TopLevel/getCmekSettings#google.logging.v2.ConfigServiceV2.GetCmekSettings) to obtain the service account ID.
+               See [Enabling CMEK for Logging Buckets](https://cloud.google.com/logging/docs/routing/managed-encryption-storage) for more information.
         """
         pulumi.set(__self__, "kms_key_name", kms_key_name)
         if kms_key_version_name is not None:
@@ -252,6 +303,14 @@ class FolderBucketConfigCmekSettingsArgs:
     @property
     @pulumi.getter(name="kmsKeyName")
     def kms_key_name(self) -> pulumi.Input[str]:
+        """
+        The resource name for the configured Cloud KMS key.
+        KMS key name format:
+        "projects/[PROJECT_ID]/locations/[LOCATION]/keyRings/[KEYRING]/cryptoKeys/[KEY]"
+        To enable CMEK for the bucket, set this field to a valid kmsKeyName for which the associated service account has the required cloudkms.cryptoKeyEncrypterDecrypter roles assigned for the key.
+        The Cloud KMS key used by the bucket can be updated by changing the kmsKeyName to a new valid key name. Encryption operations that are in progress will be completed with the key that was in use when they started. Decryption operations will be completed using the key that was used at the time of encryption unless access to that key has been revoked.
+        See [Enabling CMEK for Logging Buckets](https://cloud.google.com/logging/docs/routing/managed-encryption-storage) for more information.
+        """
         return pulumi.get(self, "kms_key_name")
 
     @kms_key_name.setter
@@ -261,6 +320,14 @@ class FolderBucketConfigCmekSettingsArgs:
     @property
     @pulumi.getter(name="kmsKeyVersionName")
     def kms_key_version_name(self) -> Optional[pulumi.Input[str]]:
+        """
+        The CryptoKeyVersion resource name for the configured Cloud KMS key.
+        KMS key name format:
+        "projects/[PROJECT_ID]/locations/[LOCATION]/keyRings/[KEYRING]/cryptoKeys/[KEY]/cryptoKeyVersions/[VERSION]"
+        For example:
+        "projects/my-project/locations/us-central1/keyRings/my-ring/cryptoKeys/my-key/cryptoKeyVersions/1"
+        This is a read-only field used to convey the specific configured CryptoKeyVersion of kms_key that has been configured. It will be populated in cases where the CMEK settings are bound to a single key version.
+        """
         return pulumi.get(self, "kms_key_version_name")
 
     @kms_key_version_name.setter
@@ -282,6 +349,11 @@ class FolderBucketConfigCmekSettingsArgs:
     @property
     @pulumi.getter(name="serviceAccountId")
     def service_account_id(self) -> Optional[pulumi.Input[str]]:
+        """
+        The service account associated with a project for which CMEK will apply.
+        Before enabling CMEK for a logging bucket, you must first assign the cloudkms.cryptoKeyEncrypterDecrypter role to the service account associated with the project for which CMEK will apply. Use [v2.getCmekSettings](https://cloud.google.com/logging/docs/reference/v2/rest/v2/TopLevel/getCmekSettings#google.logging.v2.ConfigServiceV2.GetCmekSettings) to obtain the service account ID.
+        See [Enabling CMEK for Logging Buckets](https://cloud.google.com/logging/docs/routing/managed-encryption-storage) for more information.
+        """
         return pulumi.get(self, "service_account_id")
 
     @service_account_id.setter
@@ -828,7 +900,22 @@ class OrganizationBucketConfigCmekSettingsArgs:
                  name: Optional[pulumi.Input[str]] = None,
                  service_account_id: Optional[pulumi.Input[str]] = None):
         """
+        :param pulumi.Input[str] kms_key_name: The resource name for the configured Cloud KMS key.
+               KMS key name format:
+               "projects/[PROJECT_ID]/locations/[LOCATION]/keyRings/[KEYRING]/cryptoKeys/[KEY]"
+               To enable CMEK for the bucket, set this field to a valid kmsKeyName for which the associated service account has the required cloudkms.cryptoKeyEncrypterDecrypter roles assigned for the key.
+               The Cloud KMS key used by the bucket can be updated by changing the kmsKeyName to a new valid key name. Encryption operations that are in progress will be completed with the key that was in use when they started. Decryption operations will be completed using the key that was used at the time of encryption unless access to that key has been revoked.
+               See [Enabling CMEK for Logging Buckets](https://cloud.google.com/logging/docs/routing/managed-encryption-storage) for more information.
+        :param pulumi.Input[str] kms_key_version_name: The CryptoKeyVersion resource name for the configured Cloud KMS key.
+               KMS key name format:
+               "projects/[PROJECT_ID]/locations/[LOCATION]/keyRings/[KEYRING]/cryptoKeys/[KEY]/cryptoKeyVersions/[VERSION]"
+               For example:
+               "projects/my-project/locations/us-central1/keyRings/my-ring/cryptoKeys/my-key/cryptoKeyVersions/1"
+               This is a read-only field used to convey the specific configured CryptoKeyVersion of kms_key that has been configured. It will be populated in cases where the CMEK settings are bound to a single key version.
         :param pulumi.Input[str] name: The resource name of the bucket. For example: "organizations/my-organization-id/locations/my-location/buckets/my-bucket-id"
+        :param pulumi.Input[str] service_account_id: The service account associated with a project for which CMEK will apply.
+               Before enabling CMEK for a logging bucket, you must first assign the cloudkms.cryptoKeyEncrypterDecrypter role to the service account associated with the project for which CMEK will apply. Use [v2.getCmekSettings](https://cloud.google.com/logging/docs/reference/v2/rest/v2/TopLevel/getCmekSettings#google.logging.v2.ConfigServiceV2.GetCmekSettings) to obtain the service account ID.
+               See [Enabling CMEK for Logging Buckets](https://cloud.google.com/logging/docs/routing/managed-encryption-storage) for more information.
         """
         pulumi.set(__self__, "kms_key_name", kms_key_name)
         if kms_key_version_name is not None:
@@ -841,6 +928,14 @@ class OrganizationBucketConfigCmekSettingsArgs:
     @property
     @pulumi.getter(name="kmsKeyName")
     def kms_key_name(self) -> pulumi.Input[str]:
+        """
+        The resource name for the configured Cloud KMS key.
+        KMS key name format:
+        "projects/[PROJECT_ID]/locations/[LOCATION]/keyRings/[KEYRING]/cryptoKeys/[KEY]"
+        To enable CMEK for the bucket, set this field to a valid kmsKeyName for which the associated service account has the required cloudkms.cryptoKeyEncrypterDecrypter roles assigned for the key.
+        The Cloud KMS key used by the bucket can be updated by changing the kmsKeyName to a new valid key name. Encryption operations that are in progress will be completed with the key that was in use when they started. Decryption operations will be completed using the key that was used at the time of encryption unless access to that key has been revoked.
+        See [Enabling CMEK for Logging Buckets](https://cloud.google.com/logging/docs/routing/managed-encryption-storage) for more information.
+        """
         return pulumi.get(self, "kms_key_name")
 
     @kms_key_name.setter
@@ -850,6 +945,14 @@ class OrganizationBucketConfigCmekSettingsArgs:
     @property
     @pulumi.getter(name="kmsKeyVersionName")
     def kms_key_version_name(self) -> Optional[pulumi.Input[str]]:
+        """
+        The CryptoKeyVersion resource name for the configured Cloud KMS key.
+        KMS key name format:
+        "projects/[PROJECT_ID]/locations/[LOCATION]/keyRings/[KEYRING]/cryptoKeys/[KEY]/cryptoKeyVersions/[VERSION]"
+        For example:
+        "projects/my-project/locations/us-central1/keyRings/my-ring/cryptoKeys/my-key/cryptoKeyVersions/1"
+        This is a read-only field used to convey the specific configured CryptoKeyVersion of kms_key that has been configured. It will be populated in cases where the CMEK settings are bound to a single key version.
+        """
         return pulumi.get(self, "kms_key_version_name")
 
     @kms_key_version_name.setter
@@ -871,6 +974,11 @@ class OrganizationBucketConfigCmekSettingsArgs:
     @property
     @pulumi.getter(name="serviceAccountId")
     def service_account_id(self) -> Optional[pulumi.Input[str]]:
+        """
+        The service account associated with a project for which CMEK will apply.
+        Before enabling CMEK for a logging bucket, you must first assign the cloudkms.cryptoKeyEncrypterDecrypter role to the service account associated with the project for which CMEK will apply. Use [v2.getCmekSettings](https://cloud.google.com/logging/docs/reference/v2/rest/v2/TopLevel/getCmekSettings#google.logging.v2.ConfigServiceV2.GetCmekSettings) to obtain the service account ID.
+        See [Enabling CMEK for Logging Buckets](https://cloud.google.com/logging/docs/routing/managed-encryption-storage) for more information.
+        """
         return pulumi.get(self, "service_account_id")
 
     @service_account_id.setter

pulumi_gcp/logging/billing_account_bucket_config.py

@@ -312,15 +312,7 @@ class BillingAccountBucketConfig(pulumi.CustomResource):
 
         ## Import
 
-        This resource can be imported using the following format* `billingAccounts/{{billingAccount}}/locations/{{location}}/buckets/{{bucket_id}}` In Terraform v1.5.0 and later, use an [`import` block](https://developer.hashicorp.com/terraform/language/import) to import this resource using one of the formats above. For exampletf import {
-
-         id = "billingAccounts/{{billingAccount}}/locations/{{location}}/buckets/{{bucket_id}}"
-
-         to = google_logging_billing_account_bucket_config.default }
-
-        ```sh
-         $ pulumi import gcp:logging/billingAccountBucketConfig:BillingAccountBucketConfig When using the [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import), this resource can be imported using one of the formats above. For example
-        ```
+        This resource can be imported using the following format* `billingAccounts/{{billingAccount}}/locations/{{location}}/buckets/{{bucket_id}}` When using the `pulumi import` command, this resource can be imported using one of the formats above. For example
 
         ```sh
          $ pulumi import gcp:logging/billingAccountBucketConfig:BillingAccountBucketConfig default billingAccounts/{{billingAccount}}/locations/{{location}}/buckets/{{bucket_id}}
@@ -353,15 +345,7 @@ class BillingAccountBucketConfig(pulumi.CustomResource):
 
         ## Import
 
-        This resource can be imported using the following format* `billingAccounts/{{billingAccount}}/locations/{{location}}/buckets/{{bucket_id}}` In Terraform v1.5.0 and later, use an [`import` block](https://developer.hashicorp.com/terraform/language/import) to import this resource using one of the formats above. For exampletf import {
-
-         id = "billingAccounts/{{billingAccount}}/locations/{{location}}/buckets/{{bucket_id}}"
-
-         to = google_logging_billing_account_bucket_config.default }
-
-        ```sh
-         $ pulumi import gcp:logging/billingAccountBucketConfig:BillingAccountBucketConfig When using the [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import), this resource can be imported using one of the formats above. For example
-        ```
+        This resource can be imported using the following format* `billingAccounts/{{billingAccount}}/locations/{{location}}/buckets/{{bucket_id}}` When using the `pulumi import` command, this resource can be imported using one of the formats above. For example
 
         ```sh
          $ pulumi import gcp:logging/billingAccountBucketConfig:BillingAccountBucketConfig default billingAccounts/{{billingAccount}}/locations/{{location}}/buckets/{{bucket_id}}

pulumi_gcp/logging/billing_account_exclusion.py

@@ -223,15 +223,7 @@ class BillingAccountExclusion(pulumi.CustomResource):
 
         ## Import
 
-        Billing account logging exclusions can be imported using their URI, e.g. * `billingAccounts/{{billing_account}}/exclusions/{{name}}` In Terraform v1.5.0 and later, use an [`import` block](https://developer.hashicorp.com/terraform/language/import) to import billing account logging exclusions using one of the formats above. For exampletf import {
-
-         id = "billingAccounts/{{billing_account}}/exclusions/{{name}}"
-
-         to = google_logging_billing_account_exclusion.default }
-
-        ```sh
-         $ pulumi import gcp:logging/billingAccountExclusion:BillingAccountExclusion When using the [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import), billing account logging exclusions can be imported using one of the formats above. For example
-        ```
+        Billing account logging exclusions can be imported using their URI, e.g. * `billingAccounts/{{billing_account}}/exclusions/{{name}}` When using the `pulumi import` command, billing account logging exclusions can be imported using one of the formats above. For example
 
         ```sh
          $ pulumi import gcp:logging/billingAccountExclusion:BillingAccountExclusion default billingAccounts/{{billing_account}}/exclusions/{{name}}
@@ -269,15 +261,7 @@ class BillingAccountExclusion(pulumi.CustomResource):
 
         ## Import
 
-        Billing account logging exclusions can be imported using their URI, e.g. * `billingAccounts/{{billing_account}}/exclusions/{{name}}` In Terraform v1.5.0 and later, use an [`import` block](https://developer.hashicorp.com/terraform/language/import) to import billing account logging exclusions using one of the formats above. For exampletf import {
-
-         id = "billingAccounts/{{billing_account}}/exclusions/{{name}}"
-
-         to = google_logging_billing_account_exclusion.default }
-
-        ```sh
-         $ pulumi import gcp:logging/billingAccountExclusion:BillingAccountExclusion When using the [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import), billing account logging exclusions can be imported using one of the formats above. For example
-        ```
+        Billing account logging exclusions can be imported using their URI, e.g. * `billingAccounts/{{billing_account}}/exclusions/{{name}}` When using the `pulumi import` command, billing account logging exclusions can be imported using one of the formats above. For example
 
         ```sh
          $ pulumi import gcp:logging/billingAccountExclusion:BillingAccountExclusion default billingAccounts/{{billing_account}}/exclusions/{{name}}

pulumi_gcp/logging/billing_account_sink.py

@@ -384,15 +384,7 @@ class BillingAccountSink(pulumi.CustomResource):
 
         ## Import
 
-        Billing account logging sinks can be imported using this format* `billingAccounts/{{billing_account_id}}/sinks/{{sink_id}}` In Terraform v1.5.0 and later, use an [`import` block](https://developer.hashicorp.com/terraform/language/import) to import billing account logging sinks using one of the formats above. For exampletf import {
-
-         id = "billingAccounts/{{billing_account_id}}/sinks/{{sink_id}}"
-
-         to = google_logging_billing_account_sink.default }
-
-        ```sh
-         $ pulumi import gcp:logging/billingAccountSink:BillingAccountSink When using the [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import), billing account logging sinks can be imported using one of the formats above. For example
-        ```
+        Billing account logging sinks can be imported using this format* `billingAccounts/{{billing_account_id}}/sinks/{{sink_id}}` When using the `pulumi import` command, billing account logging sinks can be imported using one of the formats above. For example
 
         ```sh
          $ pulumi import gcp:logging/billingAccountSink:BillingAccountSink default billingAccounts/{{billing_account_id}}/sinks/{{sink_id}}
@@ -454,15 +446,7 @@ class BillingAccountSink(pulumi.CustomResource):
 
         ## Import
 
-        Billing account logging sinks can be imported using this format* `billingAccounts/{{billing_account_id}}/sinks/{{sink_id}}` In Terraform v1.5.0 and later, use an [`import` block](https://developer.hashicorp.com/terraform/language/import) to import billing account logging sinks using one of the formats above. For exampletf import {
-
-         id = "billingAccounts/{{billing_account_id}}/sinks/{{sink_id}}"
-
-         to = google_logging_billing_account_sink.default }
-
-        ```sh
-         $ pulumi import gcp:logging/billingAccountSink:BillingAccountSink When using the [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import), billing account logging sinks can be imported using one of the formats above. For example
-        ```
+        Billing account logging sinks can be imported using this format* `billingAccounts/{{billing_account_id}}/sinks/{{sink_id}}` When using the `pulumi import` command, billing account logging sinks can be imported using one of the formats above. For example
 
         ```sh
          $ pulumi import gcp:logging/billingAccountSink:BillingAccountSink default billingAccounts/{{billing_account_id}}/sinks/{{sink_id}}

pulumi_gcp/logging/folder_bucket_config.py

@@ -332,15 +332,7 @@ class FolderBucketConfig(pulumi.CustomResource):
 
         ## Import
 
-        This resource can be imported using the following format* `folders/{{folder}}/locations/{{location}}/buckets/{{bucket_id}}` In Terraform v1.5.0 and later, use an [`import` block](https://developer.hashicorp.com/terraform/language/import) to import this resource using one of the formats above. For exampletf import {
-
-         id = "folders/{{folder}}/locations/{{location}}/buckets/{{bucket_id}}"
-
-         to = google_logging_folder_bucket_config.default }
-
-        ```sh
-         $ pulumi import gcp:logging/folderBucketConfig:FolderBucketConfig When using the [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import), this resource can be imported using one of the formats above. For example
-        ```
+        This resource can be imported using the following format* `folders/{{folder}}/locations/{{location}}/buckets/{{bucket_id}}` When using the `pulumi import` command, this resource can be imported using one of the formats above. For example
 
         ```sh
          $ pulumi import gcp:logging/folderBucketConfig:FolderBucketConfig default folders/{{folder}}/locations/{{location}}/buckets/{{bucket_id}}
@@ -393,15 +385,7 @@ class FolderBucketConfig(pulumi.CustomResource):
 
         ## Import
 
-        This resource can be imported using the following format* `folders/{{folder}}/locations/{{location}}/buckets/{{bucket_id}}` In Terraform v1.5.0 and later, use an [`import` block](https://developer.hashicorp.com/terraform/language/import) to import this resource using one of the formats above. For exampletf import {
-
-         id = "folders/{{folder}}/locations/{{location}}/buckets/{{bucket_id}}"
-
-         to = google_logging_folder_bucket_config.default }
-
-        ```sh
-         $ pulumi import gcp:logging/folderBucketConfig:FolderBucketConfig When using the [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import), this resource can be imported using one of the formats above. For example
-        ```
+        This resource can be imported using the following format* `folders/{{folder}}/locations/{{location}}/buckets/{{bucket_id}}` When using the `pulumi import` command, this resource can be imported using one of the formats above. For example
 
         ```sh
          $ pulumi import gcp:logging/folderBucketConfig:FolderBucketConfig default folders/{{folder}}/locations/{{location}}/buckets/{{bucket_id}}

pulumi_gcp/logging/folder_exclusion.py

@@ -238,15 +238,7 @@ class FolderExclusion(pulumi.CustomResource):
 
         ## Import
 
-        Folder-level logging exclusions can be imported using their URI, e.g. * `folders/{{folder}}/exclusions/{{name}}` In Terraform v1.5.0 and later, use an [`import` block](https://developer.hashicorp.com/terraform/language/import) to import folder-level logging exclusions using one of the formats above. For exampletf import {
-
-         id = "folders/{{folder}}/exclusions/{{name}}"
-
-         to = google_logging_folder_exclusion.default }
-
-        ```sh
-         $ pulumi import gcp:logging/folderExclusion:FolderExclusion When using the [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import), folder-level logging exclusions can be imported using one of the formats above. For example
-        ```
+        Folder-level logging exclusions can be imported using their URI, e.g. * `folders/{{folder}}/exclusions/{{name}}` When using the `pulumi import` command, folder-level logging exclusions can be imported using one of the formats above. For example
 
         ```sh
          $ pulumi import gcp:logging/folderExclusion:FolderExclusion default folders/{{folder}}/exclusions/{{name}}
@@ -296,15 +288,7 @@ class FolderExclusion(pulumi.CustomResource):
 
         ## Import
 
-        Folder-level logging exclusions can be imported using their URI, e.g. * `folders/{{folder}}/exclusions/{{name}}` In Terraform v1.5.0 and later, use an [`import` block](https://developer.hashicorp.com/terraform/language/import) to import folder-level logging exclusions using one of the formats above. For exampletf import {
-
-         id = "folders/{{folder}}/exclusions/{{name}}"
-
-         to = google_logging_folder_exclusion.default }
-
-        ```sh
-         $ pulumi import gcp:logging/folderExclusion:FolderExclusion When using the [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import), folder-level logging exclusions can be imported using one of the formats above. For example
-        ```
+        Folder-level logging exclusions can be imported using their URI, e.g. * `folders/{{folder}}/exclusions/{{name}}` When using the `pulumi import` command, folder-level logging exclusions can be imported using one of the formats above. For example
 
         ```sh
          $ pulumi import gcp:logging/folderExclusion:FolderExclusion default folders/{{folder}}/exclusions/{{name}}

pulumi_gcp/logging/folder_settings.py

@@ -258,15 +258,7 @@ class FolderSettings(pulumi.CustomResource):
 
         ## Import
 
-        FolderSettings can be imported using any of these accepted formats* `folders/{{folder}}/settings` * `{{folder}}` In Terraform v1.5.0 and later, use an [`import` block](https://developer.hashicorp.com/terraform/language/import) to import FolderSettings using one of the formats above. For exampletf import {
-
-         id = "folders/{{folder}}/settings"
-
-         to = google_logging_folder_settings.default }
-
-        ```sh
-         $ pulumi import gcp:logging/folderSettings:FolderSettings When using the [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import), FolderSettings can be imported using one of the formats above. For example
-        ```
+        FolderSettings can be imported using any of these accepted formats* `folders/{{folder}}/settings` * `{{folder}}` When using the `pulumi import` command, FolderSettings can be imported using one of the formats above. For example
 
         ```sh
          $ pulumi import gcp:logging/folderSettings:FolderSettings default folders/{{folder}}/settings
@@ -326,15 +318,7 @@ class FolderSettings(pulumi.CustomResource):
 
         ## Import
 
-        FolderSettings can be imported using any of these accepted formats* `folders/{{folder}}/settings` * `{{folder}}` In Terraform v1.5.0 and later, use an [`import` block](https://developer.hashicorp.com/terraform/language/import) to import FolderSettings using one of the formats above. For exampletf import {
-
-         id = "folders/{{folder}}/settings"
-
-         to = google_logging_folder_settings.default }
-
-        ```sh
-         $ pulumi import gcp:logging/folderSettings:FolderSettings When using the [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import), FolderSettings can be imported using one of the formats above. For example
-        ```
+        FolderSettings can be imported using any of these accepted formats* `folders/{{folder}}/settings` * `{{folder}}` When using the `pulumi import` command, FolderSettings can be imported using one of the formats above. For example
 
         ```sh
          $ pulumi import gcp:logging/folderSettings:FolderSettings default folders/{{folder}}/settings

pulumi_gcp/logging/folder_sink.py

@@ -425,15 +425,7 @@ class FolderSink(pulumi.CustomResource):
 
         ## Import
 
-        Folder-level logging sinks can be imported using this format* `folders/{{folder_id}}/sinks/{{name}}` In Terraform v1.5.0 and later, use an [`import` block](https://developer.hashicorp.com/terraform/language/import) to import folder-level logging sinks using one of the formats above. For exampletf import {
-
-         id = "folders/{{folder_id}}/sinks/{{name}}"
-
-         to = google_logging_folder_sink.default }
-
-        ```sh
-         $ pulumi import gcp:logging/folderSink:FolderSink When using the [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import), folder-level logging sinks can be imported using one of the formats above. For example
-        ```
+        Folder-level logging sinks can be imported using this format* `folders/{{folder_id}}/sinks/{{name}}` When using the `pulumi import` command, folder-level logging sinks can be imported using one of the formats above. For example
 
         ```sh
          $ pulumi import gcp:logging/folderSink:FolderSink default folders/{{folder_id}}/sinks/{{name}}
@@ -498,15 +490,7 @@ class FolderSink(pulumi.CustomResource):
 
         ## Import
 
-        Folder-level logging sinks can be imported using this format* `folders/{{folder_id}}/sinks/{{name}}` In Terraform v1.5.0 and later, use an [`import` block](https://developer.hashicorp.com/terraform/language/import) to import folder-level logging sinks using one of the formats above. For exampletf import {
-
-         id = "folders/{{folder_id}}/sinks/{{name}}"
-
-         to = google_logging_folder_sink.default }
-
-        ```sh
-         $ pulumi import gcp:logging/folderSink:FolderSink When using the [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import), folder-level logging sinks can be imported using one of the formats above. For example
-        ```
+        Folder-level logging sinks can be imported using this format* `folders/{{folder_id}}/sinks/{{name}}` When using the `pulumi import` command, folder-level logging sinks can be imported using one of the formats above. For example
 
         ```sh
          $ pulumi import gcp:logging/folderSink:FolderSink default folders/{{folder_id}}/sinks/{{name}}

pulumi_gcp/logging/linked_dataset.py

@@ -357,15 +357,7 @@ class LinkedDataset(pulumi.CustomResource):
 
         ## Import
 
-        LinkedDataset can be imported using any of these accepted formats* `{{parent}}/locations/{{location}}/buckets/{{bucket}}/links/{{link_id}}` In Terraform v1.5.0 and later, use an [`import` block](https://developer.hashicorp.com/terraform/language/import) to import LinkedDataset using one of the formats above. For exampletf import {
-
-         id = "{{parent}}/locations/{{location}}/buckets/{{bucket}}/links/{{link_id}}"
-
-         to = google_logging_linked_dataset.default }
-
-        ```sh
-         $ pulumi import gcp:logging/linkedDataset:LinkedDataset When using the [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import), LinkedDataset can be imported using one of the formats above. For example
-        ```
+        LinkedDataset can be imported using any of these accepted formats* `{{parent}}/locations/{{location}}/buckets/{{bucket}}/links/{{link_id}}` When using the `pulumi import` command, LinkedDataset can be imported using one of the formats above. For example
 
         ```sh
          $ pulumi import gcp:logging/linkedDataset:LinkedDataset default {{parent}}/locations/{{location}}/buckets/{{bucket}}/links/{{link_id}}
@@ -440,15 +432,7 @@ class LinkedDataset(pulumi.CustomResource):
 
         ## Import
 
-        LinkedDataset can be imported using any of these accepted formats* `{{parent}}/locations/{{location}}/buckets/{{bucket}}/links/{{link_id}}` In Terraform v1.5.0 and later, use an [`import` block](https://developer.hashicorp.com/terraform/language/import) to import LinkedDataset using one of the formats above. For exampletf import {
-
-         id = "{{parent}}/locations/{{location}}/buckets/{{bucket}}/links/{{link_id}}"
-
-         to = google_logging_linked_dataset.default }
-
-        ```sh
-         $ pulumi import gcp:logging/linkedDataset:LinkedDataset When using the [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import), LinkedDataset can be imported using one of the formats above. For example
-        ```
+        LinkedDataset can be imported using any of these accepted formats* `{{parent}}/locations/{{location}}/buckets/{{bucket}}/links/{{link_id}}` When using the `pulumi import` command, LinkedDataset can be imported using one of the formats above. For example
 
         ```sh
          $ pulumi import gcp:logging/linkedDataset:LinkedDataset default {{parent}}/locations/{{location}}/buckets/{{bucket}}/links/{{link_id}}

pulumi_gcp/logging/log_view.py

@@ -303,15 +303,7 @@ class LogView(pulumi.CustomResource):
 
         ## Import
 
-        LogView can be imported using any of these accepted formats* `{{parent}}/locations/{{location}}/buckets/{{bucket}}/views/{{name}}` In Terraform v1.5.0 and later, use an [`import` block](https://developer.hashicorp.com/terraform/language/import) to import LogView using one of the formats above. For exampletf import {
-
-         id = "{{parent}}/locations/{{location}}/buckets/{{bucket}}/views/{{name}}"
-
-         to = google_logging_log_view.default }
-
-        ```sh
-         $ pulumi import gcp:logging/logView:LogView When using the [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import), LogView can be imported using one of the formats above. For example
-        ```
+        LogView can be imported using any of these accepted formats* `{{parent}}/locations/{{location}}/buckets/{{bucket}}/views/{{name}}` When using the `pulumi import` command, LogView can be imported using one of the formats above. For example
 
         ```sh
          $ pulumi import gcp:logging/logView:LogView default {{parent}}/locations/{{location}}/buckets/{{bucket}}/views/{{name}}
@@ -364,15 +356,7 @@ class LogView(pulumi.CustomResource):
 
         ## Import
 
-        LogView can be imported using any of these accepted formats* `{{parent}}/locations/{{location}}/buckets/{{bucket}}/views/{{name}}` In Terraform v1.5.0 and later, use an [`import` block](https://developer.hashicorp.com/terraform/language/import) to import LogView using one of the formats above. For exampletf import {
-
-         id = "{{parent}}/locations/{{location}}/buckets/{{bucket}}/views/{{name}}"
-
-         to = google_logging_log_view.default }
-
-        ```sh
-         $ pulumi import gcp:logging/logView:LogView When using the [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import), LogView can be imported using one of the formats above. For example
-        ```
+        LogView can be imported using any of these accepted formats* `{{parent}}/locations/{{location}}/buckets/{{bucket}}/views/{{name}}` When using the `pulumi import` command, LogView can be imported using one of the formats above. For example
 
         ```sh
          $ pulumi import gcp:logging/logView:LogView default {{parent}}/locations/{{location}}/buckets/{{bucket}}/views/{{name}}

pulumi_gcp/logging/metric.py

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

pulumi_gcp/logging/organization_bucket_config.py

@@ -330,15 +330,7 @@ class OrganizationBucketConfig(pulumi.CustomResource):
 
         ## Import
 
-        This resource can be imported using the following format* `organizations/{{organization}}/locations/{{location}}/buckets/{{bucket_id}}` In Terraform v1.5.0 and later, use an [`import` block](https://developer.hashicorp.com/terraform/language/import) to import this resource using one of the formats above. For exampletf import {
-
-         id = "organizations/{{organization}}/locations/{{location}}/buckets/{{bucket_id}}"
-
-         to = google_logging_organization_bucket_config.default }
-
-        ```sh
-         $ pulumi import gcp:logging/organizationBucketConfig:OrganizationBucketConfig When using the [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import), this resource can be imported using one of the formats above. For example
-        ```
+        This resource can be imported using the following format* `organizations/{{organization}}/locations/{{location}}/buckets/{{bucket_id}}` When using the `pulumi import` command, this resource can be imported using one of the formats above. For example
 
         ```sh
          $ pulumi import gcp:logging/organizationBucketConfig:OrganizationBucketConfig default organizations/{{organization}}/locations/{{location}}/buckets/{{bucket_id}}
@@ -389,15 +381,7 @@ class OrganizationBucketConfig(pulumi.CustomResource):
 
         ## Import
 
-        This resource can be imported using the following format* `organizations/{{organization}}/locations/{{location}}/buckets/{{bucket_id}}` In Terraform v1.5.0 and later, use an [`import` block](https://developer.hashicorp.com/terraform/language/import) to import this resource using one of the formats above. For exampletf import {
-
-         id = "organizations/{{organization}}/locations/{{location}}/buckets/{{bucket_id}}"
-
-         to = google_logging_organization_bucket_config.default }
-
-        ```sh
-         $ pulumi import gcp:logging/organizationBucketConfig:OrganizationBucketConfig When using the [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import), this resource can be imported using one of the formats above. For example
-        ```
+        This resource can be imported using the following format* `organizations/{{organization}}/locations/{{location}}/buckets/{{bucket_id}}` When using the `pulumi import` command, this resource can be imported using one of the formats above. For example
 
         ```sh
          $ pulumi import gcp:logging/organizationBucketConfig:OrganizationBucketConfig default organizations/{{organization}}/locations/{{location}}/buckets/{{bucket_id}}