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

pulumi_gcp/logging/organization_exclusion.py

@@ -231,15 +231,7 @@ class OrganizationExclusion(pulumi.CustomResource):
 
         ## Import
 
-        Organization-level logging exclusions can be imported using their URI, e.g. * `organizations/{{organization}}/exclusions/{{name}}` In Terraform v1.5.0 and later, use an [`import` block](https://developer.hashicorp.com/terraform/language/import) to import organization-level logging exclusions using one of the formats above. For exampletf import {
-
-         id = "organizations/{{organization}}/exclusions/{{name}}"
-
-         to = google_logging_organization_exclusion.default }
-
-        ```sh
-         $ pulumi import gcp:logging/organizationExclusion:OrganizationExclusion When using the [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import), organization-level logging exclusions can be imported using one of the formats above. For example
-        ```
+        Organization-level logging exclusions can be imported using their URI, e.g. * `organizations/{{organization}}/exclusions/{{name}}` When using the `pulumi import` command, organization-level logging exclusions can be imported using one of the formats above. For example
 
         ```sh
          $ pulumi import gcp:logging/organizationExclusion:OrganizationExclusion default organizations/{{organization}}/exclusions/{{name}}
@@ -285,15 +277,7 @@ class OrganizationExclusion(pulumi.CustomResource):
 
         ## Import
 
-        Organization-level logging exclusions can be imported using their URI, e.g. * `organizations/{{organization}}/exclusions/{{name}}` In Terraform v1.5.0 and later, use an [`import` block](https://developer.hashicorp.com/terraform/language/import) to import organization-level logging exclusions using one of the formats above. For exampletf import {
-
-         id = "organizations/{{organization}}/exclusions/{{name}}"
-
-         to = google_logging_organization_exclusion.default }
-
-        ```sh
-         $ pulumi import gcp:logging/organizationExclusion:OrganizationExclusion When using the [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import), organization-level logging exclusions can be imported using one of the formats above. For example
-        ```
+        Organization-level logging exclusions can be imported using their URI, e.g. * `organizations/{{organization}}/exclusions/{{name}}` When using the `pulumi import` command, organization-level logging exclusions can be imported using one of the formats above. For example
 
         ```sh
          $ pulumi import gcp:logging/organizationExclusion:OrganizationExclusion default organizations/{{organization}}/exclusions/{{name}}

pulumi_gcp/logging/organization_settings.py

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

pulumi_gcp/logging/organization_sink.py

@@ -418,15 +418,7 @@ class OrganizationSink(pulumi.CustomResource):
 
         ## Import
 
-        Organization-level logging sinks can be imported using this format* `organizations/{{organization_id}}/sinks/{{sink_id}}` In Terraform v1.5.0 and later, use an [`import` block](https://developer.hashicorp.com/terraform/language/import) to import organization-level logging sinks using one of the formats above. For exampletf import {
-
-         id = "organizations/{{organization_id}}/sinks/{{sink_id}}"
-
-         to = google_logging_organization_sink.default }
-
-        ```sh
-         $ pulumi import gcp:logging/organizationSink:OrganizationSink When using the [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import), organization-level logging sinks can be imported using one of the formats above. For example
-        ```
+        Organization-level logging sinks can be imported using this format* `organizations/{{organization_id}}/sinks/{{sink_id}}` When using the `pulumi import` command, organization-level logging sinks can be imported using one of the formats above. For example
 
         ```sh
          $ pulumi import gcp:logging/organizationSink:OrganizationSink default organizations/{{organization_id}}/sinks/{{sink_id}}
@@ -487,15 +479,7 @@ class OrganizationSink(pulumi.CustomResource):
 
         ## Import
 
-        Organization-level logging sinks can be imported using this format* `organizations/{{organization_id}}/sinks/{{sink_id}}` In Terraform v1.5.0 and later, use an [`import` block](https://developer.hashicorp.com/terraform/language/import) to import organization-level logging sinks using one of the formats above. For exampletf import {
-
-         id = "organizations/{{organization_id}}/sinks/{{sink_id}}"
-
-         to = google_logging_organization_sink.default }
-
-        ```sh
-         $ pulumi import gcp:logging/organizationSink:OrganizationSink When using the [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import), organization-level logging sinks can be imported using one of the formats above. For example
-        ```
+        Organization-level logging sinks can be imported using this format* `organizations/{{organization_id}}/sinks/{{sink_id}}` When using the `pulumi import` command, organization-level logging sinks can be imported using one of the formats above. For example
 
         ```sh
          $ pulumi import gcp:logging/organizationSink:OrganizationSink default organizations/{{organization_id}}/sinks/{{sink_id}}

pulumi_gcp/logging/outputs.py

@@ -67,7 +67,22 @@ class BillingAccountBucketConfigCmekSettings(dict):
                  name: Optional[str] = None,
                  service_account_id: Optional[str] = None):
         """
+        :param 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 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 str name: The resource name of the bucket. For example: "projects/my-project-id/locations/my-location/buckets/my-bucket-id"
+        :param 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:
@@ -80,11 +95,27 @@ class BillingAccountBucketConfigCmekSettings(dict):
     @property
     @pulumi.getter(name="kmsKeyName")
     def kms_key_name(self) -> 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")
 
     @property
     @pulumi.getter(name="kmsKeyVersionName")
     def kms_key_version_name(self) -> Optional[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")
 
     @property
@@ -98,6 +129,11 @@ class BillingAccountBucketConfigCmekSettings(dict):
     @property
     @pulumi.getter(name="serviceAccountId")
     def service_account_id(self) -> Optional[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")
 
 
@@ -274,7 +310,22 @@ class FolderBucketConfigCmekSettings(dict):
                  name: Optional[str] = None,
                  service_account_id: Optional[str] = None):
         """
+        :param 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 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 str name: The resource name of the bucket. For example: "folders/my-folder-id/locations/my-location/buckets/my-bucket-id"
+        :param 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:
@@ -287,11 +338,27 @@ class FolderBucketConfigCmekSettings(dict):
     @property
     @pulumi.getter(name="kmsKeyName")
     def kms_key_name(self) -> 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")
 
     @property
     @pulumi.getter(name="kmsKeyVersionName")
     def kms_key_version_name(self) -> Optional[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")
 
     @property
@@ -305,6 +372,11 @@ class FolderBucketConfigCmekSettings(dict):
     @property
     @pulumi.getter(name="serviceAccountId")
     def service_account_id(self) -> Optional[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")
 
 
@@ -910,7 +982,22 @@ class OrganizationBucketConfigCmekSettings(dict):
                  name: Optional[str] = None,
                  service_account_id: Optional[str] = None):
         """
+        :param 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 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 str name: The resource name of the bucket. For example: "organizations/my-organization-id/locations/my-location/buckets/my-bucket-id"
+        :param 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:
@@ -923,11 +1010,27 @@ class OrganizationBucketConfigCmekSettings(dict):
     @property
     @pulumi.getter(name="kmsKeyName")
     def kms_key_name(self) -> 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")
 
     @property
     @pulumi.getter(name="kmsKeyVersionName")
     def kms_key_version_name(self) -> Optional[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")
 
     @property
@@ -941,6 +1044,11 @@ class OrganizationBucketConfigCmekSettings(dict):
     @property
     @pulumi.getter(name="serviceAccountId")
     def service_account_id(self) -> Optional[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")
 
 

pulumi_gcp/logging/project_bucket_config.py

@@ -370,15 +370,7 @@ class ProjectBucketConfig(pulumi.CustomResource):
 
         ## Import
 
-        This resource can be imported using the following format* `projects/{{project}}/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 = "projects/{{project}}/locations/{{location}}/buckets/{{bucket_id}}"
-
-         to = google_logging_project_bucket_config.default }
-
-        ```sh
-         $ pulumi import gcp:logging/projectBucketConfig:ProjectBucketConfig 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* `projects/{{project}}/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/projectBucketConfig:ProjectBucketConfig default projects/{{project}}/locations/{{location}}/buckets/{{bucket_id}}
@@ -411,15 +403,7 @@ class ProjectBucketConfig(pulumi.CustomResource):
 
         ## Import
 
-        This resource can be imported using the following format* `projects/{{project}}/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 = "projects/{{project}}/locations/{{location}}/buckets/{{bucket_id}}"
-
-         to = google_logging_project_bucket_config.default }
-
-        ```sh
-         $ pulumi import gcp:logging/projectBucketConfig:ProjectBucketConfig 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* `projects/{{project}}/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/projectBucketConfig:ProjectBucketConfig default projects/{{project}}/locations/{{location}}/buckets/{{bucket_id}}

pulumi_gcp/logging/project_exclusion.py

@@ -235,15 +235,7 @@ class ProjectExclusion(pulumi.CustomResource):
 
         ## Import
 
-        Project-level logging exclusions can be imported using their URI, e.g. * `projects/{{project_id}}/exclusions/{{name}}` In Terraform v1.5.0 and later, use an [`import` block](https://developer.hashicorp.com/terraform/language/import) to import project-level logging exclusions using one of the formats above. For exampletf import {
-
-         id = "projects/{{project_id}}/exclusions/{{name}}"
-
-         to = google_logging_project_exclusion.default }
-
-        ```sh
-         $ pulumi import gcp:logging/projectExclusion:ProjectExclusion When using the [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import), project-level logging exclusions can be imported using one of the formats above. For example
-        ```
+        Project-level logging exclusions can be imported using their URI, e.g. * `projects/{{project_id}}/exclusions/{{name}}` When using the `pulumi import` command, project-level logging exclusions can be imported using one of the formats above. For example
 
         ```sh
          $ pulumi import gcp:logging/projectExclusion:ProjectExclusion default projects/{{project_id}}/exclusions/{{name}}
@@ -289,15 +281,7 @@ class ProjectExclusion(pulumi.CustomResource):
 
         ## Import
 
-        Project-level logging exclusions can be imported using their URI, e.g. * `projects/{{project_id}}/exclusions/{{name}}` In Terraform v1.5.0 and later, use an [`import` block](https://developer.hashicorp.com/terraform/language/import) to import project-level logging exclusions using one of the formats above. For exampletf import {
-
-         id = "projects/{{project_id}}/exclusions/{{name}}"
-
-         to = google_logging_project_exclusion.default }
-
-        ```sh
-         $ pulumi import gcp:logging/projectExclusion:ProjectExclusion When using the [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import), project-level logging exclusions can be imported using one of the formats above. For example
-        ```
+        Project-level logging exclusions can be imported using their URI, e.g. * `projects/{{project_id}}/exclusions/{{name}}` When using the `pulumi import` command, project-level logging exclusions can be imported using one of the formats above. For example
 
         ```sh
          $ pulumi import gcp:logging/projectExclusion:ProjectExclusion default projects/{{project_id}}/exclusions/{{name}}

pulumi_gcp/logging/project_sink.py

@@ -449,15 +449,7 @@ class ProjectSink(pulumi.CustomResource):
         """
         ## Import
 
-        Project-level logging sinks can be imported using their URI, e.g. * `projects/{{project_id}}/sinks/{{name}}` In Terraform v1.5.0 and later, use an [`import` block](https://developer.hashicorp.com/terraform/language/import) to import project-level logging sinks using one of the formats above. For exampletf import {
-
-         id = "projects/{{project_id}}/sinks/{{name}}"
-
-         to = google_logging_project_sink.default }
-
-        ```sh
-         $ pulumi import gcp:logging/projectSink:ProjectSink When using the [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import), project-level logging sinks can be imported using one of the formats above. For example
-        ```
+        Project-level logging sinks can be imported using their URI, e.g. * `projects/{{project_id}}/sinks/{{name}}` When using the `pulumi import` command, project-level logging sinks can be imported using one of the formats above. For example
 
         ```sh
          $ pulumi import gcp:logging/projectSink:ProjectSink default projects/{{project_id}}/sinks/{{name}}
@@ -501,15 +493,7 @@ class ProjectSink(pulumi.CustomResource):
         """
         ## Import
 
-        Project-level logging sinks can be imported using their URI, e.g. * `projects/{{project_id}}/sinks/{{name}}` In Terraform v1.5.0 and later, use an [`import` block](https://developer.hashicorp.com/terraform/language/import) to import project-level logging sinks using one of the formats above. For exampletf import {
-
-         id = "projects/{{project_id}}/sinks/{{name}}"
-
-         to = google_logging_project_sink.default }
-
-        ```sh
-         $ pulumi import gcp:logging/projectSink:ProjectSink When using the [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import), project-level logging sinks can be imported using one of the formats above. For example
-        ```
+        Project-level logging sinks can be imported using their URI, e.g. * `projects/{{project_id}}/sinks/{{name}}` When using the `pulumi import` command, project-level logging sinks can be imported using one of the formats above. For example
 
         ```sh
          $ pulumi import gcp:logging/projectSink:ProjectSink default projects/{{project_id}}/sinks/{{name}}

pulumi_gcp/looker/instance.py

@@ -882,15 +882,7 @@ class Instance(pulumi.CustomResource):
 
         ## Import
 
-        Instance can be imported using any of these accepted formats* `projects/{{project}}/locations/{{region}}/instances/{{name}}` * `{{project}}/{{region}}/{{name}}` * `{{region}}/{{name}}` * `{{name}}` In Terraform v1.5.0 and later, use an [`import` block](https://developer.hashicorp.com/terraform/language/import) to import Instance using one of the formats above. For exampletf import {
-
-         id = "projects/{{project}}/locations/{{region}}/instances/{{name}}"
-
-         to = google_looker_instance.default }
-
-        ```sh
-         $ pulumi import gcp:looker/instance:Instance When using the [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import), Instance can be imported using one of the formats above. For example
-        ```
+        Instance can be imported using any of these accepted formats* `projects/{{project}}/locations/{{region}}/instances/{{name}}` * `{{project}}/{{region}}/{{name}}` * `{{region}}/{{name}}` * `{{name}}` When using the `pulumi import` command, Instance can be imported using one of the formats above. For example
 
         ```sh
          $ pulumi import gcp:looker/instance:Instance default projects/{{project}}/locations/{{region}}/instances/{{name}}
@@ -1107,15 +1099,7 @@ class Instance(pulumi.CustomResource):
 
         ## Import
 
-        Instance can be imported using any of these accepted formats* `projects/{{project}}/locations/{{region}}/instances/{{name}}` * `{{project}}/{{region}}/{{name}}` * `{{region}}/{{name}}` * `{{name}}` In Terraform v1.5.0 and later, use an [`import` block](https://developer.hashicorp.com/terraform/language/import) to import Instance using one of the formats above. For exampletf import {
-
-         id = "projects/{{project}}/locations/{{region}}/instances/{{name}}"
-
-         to = google_looker_instance.default }
-
-        ```sh
-         $ pulumi import gcp:looker/instance:Instance When using the [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import), Instance can be imported using one of the formats above. For example
-        ```
+        Instance can be imported using any of these accepted formats* `projects/{{project}}/locations/{{region}}/instances/{{name}}` * `{{project}}/{{region}}/{{name}}` * `{{region}}/{{name}}` * `{{name}}` When using the `pulumi import` command, Instance can be imported using one of the formats above. For example
 
         ```sh
          $ pulumi import gcp:looker/instance:Instance default projects/{{project}}/locations/{{region}}/instances/{{name}}