pulumi-gcp 7.13.0__py3-none-any.whl → 7.14.0__py3-none-any.whl

pulumi_gcp/dataproc/metastore_service_iam_member.py

@@ -307,6 +307,7 @@ class MetastoreServiceIamMember(pulumi.CustomResource):
 
         ## google\\_dataproc\\_metastore\\_service\\_iam\\_policy
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_gcp as gcp
@@ -321,9 +322,11 @@ class MetastoreServiceIamMember(pulumi.CustomResource):
             service_id=default["serviceId"],
             policy_data=admin.policy_data)
         ```
+        <!--End PulumiCodeChooser -->
 
         ## google\\_dataproc\\_metastore\\_service\\_iam\\_binding
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_gcp as gcp
@@ -335,9 +338,11 @@ class MetastoreServiceIamMember(pulumi.CustomResource):
             role="roles/viewer",
             members=["user:jane@example.com"])
         ```
+        <!--End PulumiCodeChooser -->
 
         ## google\\_dataproc\\_metastore\\_service\\_iam\\_member
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_gcp as gcp
@@ -349,44 +354,45 @@ class MetastoreServiceIamMember(pulumi.CustomResource):
             role="roles/viewer",
             member="user:jane@example.com")
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Import
 
         For all import syntaxes, the "resource in question" can take any of the following forms:
 
-         * projects/{{project}}/locations/{{location}}/services/{{service_id}}
+        * projects/{{project}}/locations/{{location}}/services/{{service_id}}
 
-         * {{project}}/{{location}}/{{service_id}}
+        * {{project}}/{{location}}/{{service_id}}
 
-         * {{location}}/{{service_id}}
+        * {{location}}/{{service_id}}
 
-         * {{service_id}}
+        * {{service_id}}
 
-         Any variables not passed in the import command will be taken from the provider configuration.
+        Any variables not passed in the import command will be taken from the provider configuration.
 
-         Dataproc metastore service IAM resources can be imported using the resource identifiers, role, and member.
+        Dataproc metastore service IAM resources can be imported using the resource identifiers, role, and member.
 
-         IAM member imports use space-delimited identifiers: the resource in question, the role, and the member identity, e.g.
+        IAM member imports use space-delimited identifiers: the resource in question, the role, and the member identity, e.g.
 
         ```sh
         $ pulumi import gcp:dataproc/metastoreServiceIamMember:MetastoreServiceIamMember editor "projects/{{project}}/locations/{{location}}/services/{{service_id}} roles/viewer user:jane@example.com"
         ```
 
-         IAM binding imports use space-delimited identifiers: the resource in question and the role, e.g.
+        IAM binding imports use space-delimited identifiers: the resource in question and the role, e.g.
 
         ```sh
         $ pulumi import gcp:dataproc/metastoreServiceIamMember:MetastoreServiceIamMember editor "projects/{{project}}/locations/{{location}}/services/{{service_id}} roles/viewer"
         ```
 
-         IAM policy imports use the identifier of the resource in question, e.g.
+        IAM policy imports use the identifier of the resource in question, e.g.
 
         ```sh
         $ pulumi import gcp:dataproc/metastoreServiceIamMember:MetastoreServiceIamMember editor projects/{{project}}/locations/{{location}}/services/{{service_id}}
         ```
 
-         -> **Custom Roles**: If you're importing a IAM resource with a custom role, make sure to use the
+        -> **Custom Roles**: If you're importing a IAM resource with a custom role, make sure to use the
 
-        full name of the custom role, e.g. `[projects/my-project|organizations/my-org]/roles/my-custom-role`.
+         full name of the custom role, e.g. `[projects/my-project|organizations/my-org]/roles/my-custom-role`.
 
         :param str resource_name: The name of the resource.
         :param pulumi.ResourceOptions opts: Options for the resource.
@@ -434,6 +440,7 @@ class MetastoreServiceIamMember(pulumi.CustomResource):
 
         ## google\\_dataproc\\_metastore\\_service\\_iam\\_policy
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_gcp as gcp
@@ -448,9 +455,11 @@ class MetastoreServiceIamMember(pulumi.CustomResource):
             service_id=default["serviceId"],
             policy_data=admin.policy_data)
         ```
+        <!--End PulumiCodeChooser -->
 
         ## google\\_dataproc\\_metastore\\_service\\_iam\\_binding
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_gcp as gcp
@@ -462,9 +471,11 @@ class MetastoreServiceIamMember(pulumi.CustomResource):
             role="roles/viewer",
             members=["user:jane@example.com"])
         ```
+        <!--End PulumiCodeChooser -->
 
         ## google\\_dataproc\\_metastore\\_service\\_iam\\_member
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_gcp as gcp
@@ -476,44 +487,45 @@ class MetastoreServiceIamMember(pulumi.CustomResource):
             role="roles/viewer",
             member="user:jane@example.com")
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Import
 
         For all import syntaxes, the "resource in question" can take any of the following forms:
 
-         * projects/{{project}}/locations/{{location}}/services/{{service_id}}
+        * projects/{{project}}/locations/{{location}}/services/{{service_id}}
 
-         * {{project}}/{{location}}/{{service_id}}
+        * {{project}}/{{location}}/{{service_id}}
 
-         * {{location}}/{{service_id}}
+        * {{location}}/{{service_id}}
 
-         * {{service_id}}
+        * {{service_id}}
 
-         Any variables not passed in the import command will be taken from the provider configuration.
+        Any variables not passed in the import command will be taken from the provider configuration.
 
-         Dataproc metastore service IAM resources can be imported using the resource identifiers, role, and member.
+        Dataproc metastore service IAM resources can be imported using the resource identifiers, role, and member.
 
-         IAM member imports use space-delimited identifiers: the resource in question, the role, and the member identity, e.g.
+        IAM member imports use space-delimited identifiers: the resource in question, the role, and the member identity, e.g.
 
         ```sh
         $ pulumi import gcp:dataproc/metastoreServiceIamMember:MetastoreServiceIamMember editor "projects/{{project}}/locations/{{location}}/services/{{service_id}} roles/viewer user:jane@example.com"
         ```
 
-         IAM binding imports use space-delimited identifiers: the resource in question and the role, e.g.
+        IAM binding imports use space-delimited identifiers: the resource in question and the role, e.g.
 
         ```sh
         $ pulumi import gcp:dataproc/metastoreServiceIamMember:MetastoreServiceIamMember editor "projects/{{project}}/locations/{{location}}/services/{{service_id}} roles/viewer"
         ```
 
-         IAM policy imports use the identifier of the resource in question, e.g.
+        IAM policy imports use the identifier of the resource in question, e.g.
 
         ```sh
         $ pulumi import gcp:dataproc/metastoreServiceIamMember:MetastoreServiceIamMember editor projects/{{project}}/locations/{{location}}/services/{{service_id}}
         ```
 
-         -> **Custom Roles**: If you're importing a IAM resource with a custom role, make sure to use the
+        -> **Custom Roles**: If you're importing a IAM resource with a custom role, make sure to use the
 
-        full name of the custom role, e.g. `[projects/my-project|organizations/my-org]/roles/my-custom-role`.
+         full name of the custom role, e.g. `[projects/my-project|organizations/my-org]/roles/my-custom-role`.
 
         :param str resource_name: The name of the resource.
         :param MetastoreServiceIamMemberArgs args: The arguments to use to populate this resource's properties.

pulumi_gcp/dataproc/metastore_service_iam_policy.py

@@ -252,6 +252,7 @@ class MetastoreServiceIamPolicy(pulumi.CustomResource):
 
         ## google\\_dataproc\\_metastore\\_service\\_iam\\_policy
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_gcp as gcp
@@ -266,9 +267,11 @@ class MetastoreServiceIamPolicy(pulumi.CustomResource):
             service_id=default["serviceId"],
             policy_data=admin.policy_data)
         ```
+        <!--End PulumiCodeChooser -->
 
         ## google\\_dataproc\\_metastore\\_service\\_iam\\_binding
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_gcp as gcp
@@ -280,9 +283,11 @@ class MetastoreServiceIamPolicy(pulumi.CustomResource):
             role="roles/viewer",
             members=["user:jane@example.com"])
         ```
+        <!--End PulumiCodeChooser -->
 
         ## google\\_dataproc\\_metastore\\_service\\_iam\\_member
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_gcp as gcp
@@ -294,44 +299,45 @@ class MetastoreServiceIamPolicy(pulumi.CustomResource):
             role="roles/viewer",
             member="user:jane@example.com")
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Import
 
         For all import syntaxes, the "resource in question" can take any of the following forms:
 
-         * projects/{{project}}/locations/{{location}}/services/{{service_id}}
+        * projects/{{project}}/locations/{{location}}/services/{{service_id}}
 
-         * {{project}}/{{location}}/{{service_id}}
+        * {{project}}/{{location}}/{{service_id}}
 
-         * {{location}}/{{service_id}}
+        * {{location}}/{{service_id}}
 
-         * {{service_id}}
+        * {{service_id}}
 
-         Any variables not passed in the import command will be taken from the provider configuration.
+        Any variables not passed in the import command will be taken from the provider configuration.
 
-         Dataproc metastore service IAM resources can be imported using the resource identifiers, role, and member.
+        Dataproc metastore service IAM resources can be imported using the resource identifiers, role, and member.
 
-         IAM member imports use space-delimited identifiers: the resource in question, the role, and the member identity, e.g.
+        IAM member imports use space-delimited identifiers: the resource in question, the role, and the member identity, e.g.
 
         ```sh
         $ pulumi import gcp:dataproc/metastoreServiceIamPolicy:MetastoreServiceIamPolicy editor "projects/{{project}}/locations/{{location}}/services/{{service_id}} roles/viewer user:jane@example.com"
         ```
 
-         IAM binding imports use space-delimited identifiers: the resource in question and the role, e.g.
+        IAM binding imports use space-delimited identifiers: the resource in question and the role, e.g.
 
         ```sh
         $ pulumi import gcp:dataproc/metastoreServiceIamPolicy:MetastoreServiceIamPolicy editor "projects/{{project}}/locations/{{location}}/services/{{service_id}} roles/viewer"
         ```
 
-         IAM policy imports use the identifier of the resource in question, e.g.
+        IAM policy imports use the identifier of the resource in question, e.g.
 
         ```sh
         $ pulumi import gcp:dataproc/metastoreServiceIamPolicy:MetastoreServiceIamPolicy editor projects/{{project}}/locations/{{location}}/services/{{service_id}}
         ```
 
-         -> **Custom Roles**: If you're importing a IAM resource with a custom role, make sure to use the
+        -> **Custom Roles**: If you're importing a IAM resource with a custom role, make sure to use the
 
-        full name of the custom role, e.g. `[projects/my-project|organizations/my-org]/roles/my-custom-role`.
+         full name of the custom role, e.g. `[projects/my-project|organizations/my-org]/roles/my-custom-role`.
 
         :param str resource_name: The name of the resource.
         :param pulumi.ResourceOptions opts: Options for the resource.
@@ -378,6 +384,7 @@ class MetastoreServiceIamPolicy(pulumi.CustomResource):
 
         ## google\\_dataproc\\_metastore\\_service\\_iam\\_policy
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_gcp as gcp
@@ -392,9 +399,11 @@ class MetastoreServiceIamPolicy(pulumi.CustomResource):
             service_id=default["serviceId"],
             policy_data=admin.policy_data)
         ```
+        <!--End PulumiCodeChooser -->
 
         ## google\\_dataproc\\_metastore\\_service\\_iam\\_binding
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_gcp as gcp
@@ -406,9 +415,11 @@ class MetastoreServiceIamPolicy(pulumi.CustomResource):
             role="roles/viewer",
             members=["user:jane@example.com"])
         ```
+        <!--End PulumiCodeChooser -->
 
         ## google\\_dataproc\\_metastore\\_service\\_iam\\_member
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_gcp as gcp
@@ -420,44 +431,45 @@ class MetastoreServiceIamPolicy(pulumi.CustomResource):
             role="roles/viewer",
             member="user:jane@example.com")
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Import
 
         For all import syntaxes, the "resource in question" can take any of the following forms:
 
-         * projects/{{project}}/locations/{{location}}/services/{{service_id}}
+        * projects/{{project}}/locations/{{location}}/services/{{service_id}}
 
-         * {{project}}/{{location}}/{{service_id}}
+        * {{project}}/{{location}}/{{service_id}}
 
-         * {{location}}/{{service_id}}
+        * {{location}}/{{service_id}}
 
-         * {{service_id}}
+        * {{service_id}}
 
-         Any variables not passed in the import command will be taken from the provider configuration.
+        Any variables not passed in the import command will be taken from the provider configuration.
 
-         Dataproc metastore service IAM resources can be imported using the resource identifiers, role, and member.
+        Dataproc metastore service IAM resources can be imported using the resource identifiers, role, and member.
 
-         IAM member imports use space-delimited identifiers: the resource in question, the role, and the member identity, e.g.
+        IAM member imports use space-delimited identifiers: the resource in question, the role, and the member identity, e.g.
 
         ```sh
         $ pulumi import gcp:dataproc/metastoreServiceIamPolicy:MetastoreServiceIamPolicy editor "projects/{{project}}/locations/{{location}}/services/{{service_id}} roles/viewer user:jane@example.com"
         ```
 
-         IAM binding imports use space-delimited identifiers: the resource in question and the role, e.g.
+        IAM binding imports use space-delimited identifiers: the resource in question and the role, e.g.
 
         ```sh
         $ pulumi import gcp:dataproc/metastoreServiceIamPolicy:MetastoreServiceIamPolicy editor "projects/{{project}}/locations/{{location}}/services/{{service_id}} roles/viewer"
         ```
 
-         IAM policy imports use the identifier of the resource in question, e.g.
+        IAM policy imports use the identifier of the resource in question, e.g.
 
         ```sh
         $ pulumi import gcp:dataproc/metastoreServiceIamPolicy:MetastoreServiceIamPolicy editor projects/{{project}}/locations/{{location}}/services/{{service_id}}
         ```
 
-         -> **Custom Roles**: If you're importing a IAM resource with a custom role, make sure to use the
+        -> **Custom Roles**: If you're importing a IAM resource with a custom role, make sure to use the
 
-        full name of the custom role, e.g. `[projects/my-project|organizations/my-org]/roles/my-custom-role`.
+         full name of the custom role, e.g. `[projects/my-project|organizations/my-org]/roles/my-custom-role`.
 
         :param str resource_name: The name of the resource.
         :param MetastoreServiceIamPolicyArgs args: The arguments to use to populate this resource's properties.

pulumi_gcp/dataproc/workflow_template.py

@@ -412,6 +412,7 @@ class WorkflowTemplate(pulumi.CustomResource):
 
         ## Example Usage
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_gcp as gcp
@@ -471,18 +472,19 @@ class WorkflowTemplate(pulumi.CustomResource):
                 ),
             ])
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Import
 
         WorkflowTemplate can be imported using any of these accepted formats:
 
-         * `projects/{{project}}/locations/{{location}}/workflowTemplates/{{name}}`
+        * `projects/{{project}}/locations/{{location}}/workflowTemplates/{{name}}`
 
-         * `{{project}}/{{location}}/{{name}}`
+        * `{{project}}/{{location}}/{{name}}`
 
-         * `{{location}}/{{name}}`
+        * `{{location}}/{{name}}`
 
-         When using the `pulumi import` command, WorkflowTemplate can be imported using one of the formats above. For example:
+        When using the `pulumi import` command, WorkflowTemplate can be imported using one of the formats above. For example:
 
         ```sh
         $ pulumi import gcp:dataproc/workflowTemplate:WorkflowTemplate default projects/{{project}}/locations/{{location}}/workflowTemplates/{{name}}
@@ -519,6 +521,7 @@ class WorkflowTemplate(pulumi.CustomResource):
 
         ## Example Usage
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_gcp as gcp
@@ -578,18 +581,19 @@ class WorkflowTemplate(pulumi.CustomResource):
                 ),
             ])
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Import
 
         WorkflowTemplate can be imported using any of these accepted formats:
 
-         * `projects/{{project}}/locations/{{location}}/workflowTemplates/{{name}}`
+        * `projects/{{project}}/locations/{{location}}/workflowTemplates/{{name}}`
 
-         * `{{project}}/{{location}}/{{name}}`
+        * `{{project}}/{{location}}/{{name}}`
 
-         * `{{location}}/{{name}}`
+        * `{{location}}/{{name}}`
 
-         When using the `pulumi import` command, WorkflowTemplate can be imported using one of the formats above. For example:
+        When using the `pulumi import` command, WorkflowTemplate can be imported using one of the formats above. For example:
 
         ```sh
         $ pulumi import gcp:dataproc/workflowTemplate:WorkflowTemplate default projects/{{project}}/locations/{{location}}/workflowTemplates/{{name}}

pulumi_gcp/datastore/data_store_index.py

@@ -226,8 +226,10 @@ class DataStoreIndex(pulumi.CustomResource):
         Datastore location will be the same as the App Engine location specified.
 
         ## Example Usage
+
         ### Datastore Index
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_gcp as gcp
@@ -245,18 +247,19 @@ class DataStoreIndex(pulumi.CustomResource):
                 ),
             ])
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Import
 
         Index can be imported using any of these accepted formats:
 
-         * `projects/{{project}}/indexes/{{index_id}}`
+        * `projects/{{project}}/indexes/{{index_id}}`
 
-         * `{{project}}/{{index_id}}`
+        * `{{project}}/{{index_id}}`
 
-         * `{{index_id}}`
+        * `{{index_id}}`
 
-         When using the `pulumi import` command, Index can be imported using one of the formats above. For example:
+        When using the `pulumi import` command, Index can be imported using one of the formats above. For example:
 
         ```sh
         $ pulumi import gcp:datastore/dataStoreIndex:DataStoreIndex default projects/{{project}}/indexes/{{index_id}}
@@ -306,8 +309,10 @@ class DataStoreIndex(pulumi.CustomResource):
         Datastore location will be the same as the App Engine location specified.
 
         ## Example Usage
+
         ### Datastore Index
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_gcp as gcp
@@ -325,18 +330,19 @@ class DataStoreIndex(pulumi.CustomResource):
                 ),
             ])
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Import
 
         Index can be imported using any of these accepted formats:
 
-         * `projects/{{project}}/indexes/{{index_id}}`
+        * `projects/{{project}}/indexes/{{index_id}}`
 
-         * `{{project}}/{{index_id}}`
+        * `{{project}}/{{index_id}}`
 
-         * `{{index_id}}`
+        * `{{index_id}}`
 
-         When using the `pulumi import` command, Index can be imported using one of the formats above. For example:
+        When using the `pulumi import` command, Index can be imported using one of the formats above. For example:
 
         ```sh
         $ pulumi import gcp:datastore/dataStoreIndex:DataStoreIndex default projects/{{project}}/indexes/{{index_id}}

pulumi_gcp/datastream/connection_profile.py

@@ -536,8 +536,10 @@ class ConnectionProfile(pulumi.CustomResource):
             * [Official Documentation](https://cloud.google.com/datastream/docs/create-connection-profiles)
 
         ## Example Usage
+
         ### Datastream Connection Profile Basic
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_gcp as gcp
@@ -551,8 +553,10 @@ class ConnectionProfile(pulumi.CustomResource):
                 root_path="/path",
             ))
         ```
+        <!--End PulumiCodeChooser -->
         ### Datastream Connection Profile Postgresql Private Connection
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_gcp as gcp
@@ -621,8 +625,10 @@ class ConnectionProfile(pulumi.CustomResource):
                 private_connection=private_connection.id,
             ))
         ```
+        <!--End PulumiCodeChooser -->
         ### Datastream Connection Profile Full
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_gcp as gcp
@@ -645,8 +651,10 @@ class ConnectionProfile(pulumi.CustomResource):
                 "key": "value",
             })
         ```
+        <!--End PulumiCodeChooser -->
         ### Datastream Connection Profile Postgres
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_gcp as gcp
@@ -700,18 +708,19 @@ class ConnectionProfile(pulumi.CustomResource):
                 database=db.name,
             ))
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Import
 
         ConnectionProfile can be imported using any of these accepted formats:
 
-         * `projects/{{project}}/locations/{{location}}/connectionProfiles/{{connection_profile_id}}`
+        * `projects/{{project}}/locations/{{location}}/connectionProfiles/{{connection_profile_id}}`
 
-         * `{{project}}/{{location}}/{{connection_profile_id}}`
+        * `{{project}}/{{location}}/{{connection_profile_id}}`
 
-         * `{{location}}/{{connection_profile_id}}`
+        * `{{location}}/{{connection_profile_id}}`
 
-         When using the `pulumi import` command, ConnectionProfile can be imported using one of the formats above. For example:
+        When using the `pulumi import` command, ConnectionProfile can be imported using one of the formats above. For example:
 
         ```sh
         $ pulumi import gcp:datastream/connectionProfile:ConnectionProfile default projects/{{project}}/locations/{{location}}/connectionProfiles/{{connection_profile_id}}
@@ -768,8 +777,10 @@ class ConnectionProfile(pulumi.CustomResource):
             * [Official Documentation](https://cloud.google.com/datastream/docs/create-connection-profiles)
 
         ## Example Usage
+
         ### Datastream Connection Profile Basic
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_gcp as gcp
@@ -783,8 +794,10 @@ class ConnectionProfile(pulumi.CustomResource):
                 root_path="/path",
             ))
         ```
+        <!--End PulumiCodeChooser -->
         ### Datastream Connection Profile Postgresql Private Connection
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_gcp as gcp
@@ -853,8 +866,10 @@ class ConnectionProfile(pulumi.CustomResource):
                 private_connection=private_connection.id,
             ))
         ```
+        <!--End PulumiCodeChooser -->
         ### Datastream Connection Profile Full
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_gcp as gcp
@@ -877,8 +892,10 @@ class ConnectionProfile(pulumi.CustomResource):
                 "key": "value",
             })
         ```
+        <!--End PulumiCodeChooser -->
         ### Datastream Connection Profile Postgres
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_gcp as gcp
@@ -932,18 +949,19 @@ class ConnectionProfile(pulumi.CustomResource):
                 database=db.name,
             ))
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Import
 
         ConnectionProfile can be imported using any of these accepted formats:
 
-         * `projects/{{project}}/locations/{{location}}/connectionProfiles/{{connection_profile_id}}`
+        * `projects/{{project}}/locations/{{location}}/connectionProfiles/{{connection_profile_id}}`
 
-         * `{{project}}/{{location}}/{{connection_profile_id}}`
+        * `{{project}}/{{location}}/{{connection_profile_id}}`
 
-         * `{{location}}/{{connection_profile_id}}`
+        * `{{location}}/{{connection_profile_id}}`
 
-         When using the `pulumi import` command, ConnectionProfile can be imported using one of the formats above. For example:
+        When using the `pulumi import` command, ConnectionProfile can be imported using one of the formats above. For example:
 
         ```sh
         $ pulumi import gcp:datastream/connectionProfile:ConnectionProfile default projects/{{project}}/locations/{{location}}/connectionProfiles/{{connection_profile_id}}

pulumi_gcp/datastream/get_static_ips.py

@@ -83,6 +83,7 @@ def get_static_ips(location: Optional[str] = None,
 
     ## Example Usage
 
+    <!--Start PulumiCodeChooser -->
     ```python
     import pulumi
     import pulumi_gcp as gcp
@@ -91,6 +92,7 @@ def get_static_ips(location: Optional[str] = None,
         project="my-project")
     pulumi.export("ipList", datastream_ips.static_ips)
     ```
+    <!--End PulumiCodeChooser -->
 
 
     :param str location: The location to list Datastream IPs for. For example: `us-east1`.
@@ -119,6 +121,7 @@ def get_static_ips_output(location: Optional[pulumi.Input[str]] = None,
 
     ## Example Usage
 
+    <!--Start PulumiCodeChooser -->
     ```python
     import pulumi
     import pulumi_gcp as gcp
@@ -127,6 +130,7 @@ def get_static_ips_output(location: Optional[pulumi.Input[str]] = None,
         project="my-project")
     pulumi.export("ipList", datastream_ips.static_ips)
     ```
+    <!--End PulumiCodeChooser -->
 
 
     :param str location: The location to list Datastream IPs for. For example: `us-east1`.