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

pulumi_gcp/dataflow/flex_template_job.py

@@ -74,12 +74,12 @@ class FlexTemplateJobArgs:
         :param pulumi.Input[str] region: The region in which the created job should run.
         :param pulumi.Input[str] sdk_container_image: Docker registry location of container image to use for the 'worker harness. Default is the container for the version of
                the SDK. Note this field is only valid for portable pipelines.
-        :param pulumi.Input[str] service_account_email: The Service Account email used to create the job.
+        :param pulumi.Input[str] service_account_email: Service account email to run the workers as.
         :param pulumi.Input[bool] skip_wait_on_job_termination: If true, treat DRAINING and CANCELLING as terminal job states and do not wait for further changes before removing from
                terraform state and moving on. WARNING: this will lead to job name conflicts if you do not ensure that the job names are
                different, e.g. by embedding a release ID or by using a random_id.
         :param pulumi.Input[str] staging_location: The Cloud Storage path to use for staging files. Must be a valid Cloud Storage URL, beginning with gs://.
-        :param pulumi.Input[str] subnetwork: The subnetwork to which VMs will be assigned. Should be of the form "regions/REGION/subnetworks/SUBNETWORK".
+        :param pulumi.Input[str] subnetwork: Compute Engine subnetwork for launching instances to run your pipeline.
         :param pulumi.Input[str] temp_location: The Cloud Storage path to use for temporary files. Must be a valid Cloud Storage URL, beginning with gs://.
         :param pulumi.Input[Mapping[str, Any]] transform_name_mapping: Only applicable when updating a pipeline. Map of transform name prefixes of the job to be replaced with the
                corresponding name prefixes of the new job.
@@ -368,7 +368,7 @@ class FlexTemplateJobArgs:
     @pulumi.getter(name="serviceAccountEmail")
     def service_account_email(self) -> Optional[pulumi.Input[str]]:
         """
-        The Service Account email used to create the job.
+        Service account email to run the workers as.
         """
         return pulumi.get(self, "service_account_email")
 
@@ -406,7 +406,7 @@ class FlexTemplateJobArgs:
     @pulumi.getter
     def subnetwork(self) -> Optional[pulumi.Input[str]]:
         """
-        The subnetwork to which VMs will be assigned. Should be of the form "regions/REGION/subnetworks/SUBNETWORK".
+        Compute Engine subnetwork for launching instances to run your pipeline.
         """
         return pulumi.get(self, "subnetwork")
 
@@ -512,13 +512,13 @@ class _FlexTemplateJobState:
         :param pulumi.Input[str] region: The region in which the created job should run.
         :param pulumi.Input[str] sdk_container_image: Docker registry location of container image to use for the 'worker harness. Default is the container for the version of
                the SDK. Note this field is only valid for portable pipelines.
-        :param pulumi.Input[str] service_account_email: The Service Account email used to create the job.
+        :param pulumi.Input[str] service_account_email: Service account email to run the workers as.
         :param pulumi.Input[bool] skip_wait_on_job_termination: If true, treat DRAINING and CANCELLING as terminal job states and do not wait for further changes before removing from
                terraform state and moving on. WARNING: this will lead to job name conflicts if you do not ensure that the job names are
                different, e.g. by embedding a release ID or by using a random_id.
         :param pulumi.Input[str] staging_location: The Cloud Storage path to use for staging files. Must be a valid Cloud Storage URL, beginning with gs://.
         :param pulumi.Input[str] state: The current state of the resource, selected from the [JobState enum](https://cloud.google.com/dataflow/docs/reference/rest/v1b3/projects.jobs#Job.JobState)
-        :param pulumi.Input[str] subnetwork: The subnetwork to which VMs will be assigned. Should be of the form "regions/REGION/subnetworks/SUBNETWORK".
+        :param pulumi.Input[str] subnetwork: Compute Engine subnetwork for launching instances to run your pipeline.
         :param pulumi.Input[str] temp_location: The Cloud Storage path to use for temporary files. Must be a valid Cloud Storage URL, beginning with gs://.
         :param pulumi.Input[Mapping[str, Any]] transform_name_mapping: Only applicable when updating a pipeline. Map of transform name prefixes of the job to be replaced with the
                corresponding name prefixes of the new job.
@@ -856,7 +856,7 @@ class _FlexTemplateJobState:
     @pulumi.getter(name="serviceAccountEmail")
     def service_account_email(self) -> Optional[pulumi.Input[str]]:
         """
-        The Service Account email used to create the job.
+        Service account email to run the workers as.
         """
         return pulumi.get(self, "service_account_email")
 
@@ -906,7 +906,7 @@ class _FlexTemplateJobState:
     @pulumi.getter
     def subnetwork(self) -> Optional[pulumi.Input[str]]:
         """
-        The subnetwork to which VMs will be assigned. Should be of the form "regions/REGION/subnetworks/SUBNETWORK".
+        Compute Engine subnetwork for launching instances to run your pipeline.
         """
         return pulumi.get(self, "subnetwork")
 
@@ -985,6 +985,7 @@ class FlexTemplateJob(pulumi.CustomResource):
         """
         ## Example Usage
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_gcp as gcp
@@ -996,6 +997,8 @@ class FlexTemplateJob(pulumi.CustomResource):
                 "inputSubscription": "messages",
             })
         ```
+        <!--End PulumiCodeChooser -->
+
         ## Note on "destroy" / "apply"
 
         There are many types of Dataflow jobs.  Some Dataflow jobs run constantly,
@@ -1025,6 +1028,7 @@ class FlexTemplateJob(pulumi.CustomResource):
         random_id
         resource, for example:
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_gcp as gcp
@@ -1049,6 +1053,7 @@ class FlexTemplateJob(pulumi.CustomResource):
                 "inputSubscription": big_data_job_subscription_id,
             })
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Import
 
@@ -1090,12 +1095,12 @@ class FlexTemplateJob(pulumi.CustomResource):
         :param pulumi.Input[str] region: The region in which the created job should run.
         :param pulumi.Input[str] sdk_container_image: Docker registry location of container image to use for the 'worker harness. Default is the container for the version of
                the SDK. Note this field is only valid for portable pipelines.
-        :param pulumi.Input[str] service_account_email: The Service Account email used to create the job.
+        :param pulumi.Input[str] service_account_email: Service account email to run the workers as.
         :param pulumi.Input[bool] skip_wait_on_job_termination: If true, treat DRAINING and CANCELLING as terminal job states and do not wait for further changes before removing from
                terraform state and moving on. WARNING: this will lead to job name conflicts if you do not ensure that the job names are
                different, e.g. by embedding a release ID or by using a random_id.
         :param pulumi.Input[str] staging_location: The Cloud Storage path to use for staging files. Must be a valid Cloud Storage URL, beginning with gs://.
-        :param pulumi.Input[str] subnetwork: The subnetwork to which VMs will be assigned. Should be of the form "regions/REGION/subnetworks/SUBNETWORK".
+        :param pulumi.Input[str] subnetwork: Compute Engine subnetwork for launching instances to run your pipeline.
         :param pulumi.Input[str] temp_location: The Cloud Storage path to use for temporary files. Must be a valid Cloud Storage URL, beginning with gs://.
         :param pulumi.Input[Mapping[str, Any]] transform_name_mapping: Only applicable when updating a pipeline. Map of transform name prefixes of the job to be replaced with the
                corresponding name prefixes of the new job.
@@ -1109,6 +1114,7 @@ class FlexTemplateJob(pulumi.CustomResource):
         """
         ## Example Usage
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_gcp as gcp
@@ -1120,6 +1126,8 @@ class FlexTemplateJob(pulumi.CustomResource):
                 "inputSubscription": "messages",
             })
         ```
+        <!--End PulumiCodeChooser -->
+
         ## Note on "destroy" / "apply"
 
         There are many types of Dataflow jobs.  Some Dataflow jobs run constantly,
@@ -1149,6 +1157,7 @@ class FlexTemplateJob(pulumi.CustomResource):
         random_id
         resource, for example:
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_gcp as gcp
@@ -1173,6 +1182,7 @@ class FlexTemplateJob(pulumi.CustomResource):
                 "inputSubscription": big_data_job_subscription_id,
             })
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Import
 
@@ -1343,13 +1353,13 @@ class FlexTemplateJob(pulumi.CustomResource):
         :param pulumi.Input[str] region: The region in which the created job should run.
         :param pulumi.Input[str] sdk_container_image: Docker registry location of container image to use for the 'worker harness. Default is the container for the version of
                the SDK. Note this field is only valid for portable pipelines.
-        :param pulumi.Input[str] service_account_email: The Service Account email used to create the job.
+        :param pulumi.Input[str] service_account_email: Service account email to run the workers as.
         :param pulumi.Input[bool] skip_wait_on_job_termination: If true, treat DRAINING and CANCELLING as terminal job states and do not wait for further changes before removing from
                terraform state and moving on. WARNING: this will lead to job name conflicts if you do not ensure that the job names are
                different, e.g. by embedding a release ID or by using a random_id.
         :param pulumi.Input[str] staging_location: The Cloud Storage path to use for staging files. Must be a valid Cloud Storage URL, beginning with gs://.
         :param pulumi.Input[str] state: The current state of the resource, selected from the [JobState enum](https://cloud.google.com/dataflow/docs/reference/rest/v1b3/projects.jobs#Job.JobState)
-        :param pulumi.Input[str] subnetwork: The subnetwork to which VMs will be assigned. Should be of the form "regions/REGION/subnetworks/SUBNETWORK".
+        :param pulumi.Input[str] subnetwork: Compute Engine subnetwork for launching instances to run your pipeline.
         :param pulumi.Input[str] temp_location: The Cloud Storage path to use for temporary files. Must be a valid Cloud Storage URL, beginning with gs://.
         :param pulumi.Input[Mapping[str, Any]] transform_name_mapping: Only applicable when updating a pipeline. Map of transform name prefixes of the job to be replaced with the
                corresponding name prefixes of the new job.
@@ -1579,7 +1589,7 @@ class FlexTemplateJob(pulumi.CustomResource):
     @pulumi.getter(name="serviceAccountEmail")
     def service_account_email(self) -> pulumi.Output[str]:
         """
-        The Service Account email used to create the job.
+        Service account email to run the workers as.
         """
         return pulumi.get(self, "service_account_email")
 
@@ -1613,7 +1623,7 @@ class FlexTemplateJob(pulumi.CustomResource):
     @pulumi.getter
     def subnetwork(self) -> pulumi.Output[str]:
         """
-        The subnetwork to which VMs will be assigned. Should be of the form "regions/REGION/subnetworks/SUBNETWORK".
+        Compute Engine subnetwork for launching instances to run your pipeline.
         """
         return pulumi.get(self, "subnetwork")
 

pulumi_gcp/dataflow/job.py

@@ -794,6 +794,7 @@ class Job(pulumi.CustomResource):
 
         ## Example Usage
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_gcp as gcp
@@ -807,8 +808,11 @@ class Job(pulumi.CustomResource):
                 "baz": "qux",
             })
         ```
+        <!--End PulumiCodeChooser -->
+
         ### Streaming Job
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_gcp as gcp
@@ -837,6 +841,8 @@ class Job(pulumi.CustomResource):
             },
             on_delete="cancel")
         ```
+        <!--End PulumiCodeChooser -->
+
         ## Note on "destroy" / "apply"
 
         There are many types of Dataflow jobs.  Some Dataflow jobs run constantly, getting new data from (e.g.) a GCS bucket, and outputting data continuously.  Some jobs process a set amount of data then terminate.  All jobs can fail while running due to programming errors or other issues.  In this way, Dataflow jobs are different from most other Google resources.
@@ -847,6 +853,7 @@ class Job(pulumi.CustomResource):
 
         You can potentially short-circuit the wait by setting `skip_wait_on_job_termination` to `true`, but beware that unless you take active steps to ensure that the job `name` parameter changes between instances, the name will conflict and the launch of the new job will fail. One way to do this is with a random_id resource, for example:
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_gcp as gcp
@@ -871,14 +878,15 @@ class Job(pulumi.CustomResource):
                 "inputSubscription": big_data_job_subscription_id,
             })
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Import
 
         Dataflow jobs can be imported using the job `id` e.g.
 
-         * `{{id}}`
+        * `{{id}}`
 
-         When using the `pulumi import` command, dataflow jobs can be imported using one of the formats above. For example:
+        When using the `pulumi import` command, dataflow jobs can be imported using one of the formats above. For example:
 
         ```sh
         $ pulumi import gcp:dataflow/job:Job default {{id}}
@@ -924,6 +932,7 @@ class Job(pulumi.CustomResource):
 
         ## Example Usage
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_gcp as gcp
@@ -937,8 +946,11 @@ class Job(pulumi.CustomResource):
                 "baz": "qux",
             })
         ```
+        <!--End PulumiCodeChooser -->
+
         ### Streaming Job
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_gcp as gcp
@@ -967,6 +979,8 @@ class Job(pulumi.CustomResource):
             },
             on_delete="cancel")
         ```
+        <!--End PulumiCodeChooser -->
+
         ## Note on "destroy" / "apply"
 
         There are many types of Dataflow jobs.  Some Dataflow jobs run constantly, getting new data from (e.g.) a GCS bucket, and outputting data continuously.  Some jobs process a set amount of data then terminate.  All jobs can fail while running due to programming errors or other issues.  In this way, Dataflow jobs are different from most other Google resources.
@@ -977,6 +991,7 @@ class Job(pulumi.CustomResource):
 
         You can potentially short-circuit the wait by setting `skip_wait_on_job_termination` to `true`, but beware that unless you take active steps to ensure that the job `name` parameter changes between instances, the name will conflict and the launch of the new job will fail. One way to do this is with a random_id resource, for example:
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_gcp as gcp
@@ -1001,14 +1016,15 @@ class Job(pulumi.CustomResource):
                 "inputSubscription": big_data_job_subscription_id,
             })
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Import
 
         Dataflow jobs can be imported using the job `id` e.g.
 
-         * `{{id}}`
+        * `{{id}}`
 
-         When using the `pulumi import` command, dataflow jobs can be imported using one of the formats above. For example:
+        When using the `pulumi import` command, dataflow jobs can be imported using one of the formats above. For example:
 
         ```sh
         $ pulumi import gcp:dataflow/job:Job default {{id}}

pulumi_gcp/dataflow/pipeline.py

@@ -489,8 +489,10 @@ class Pipeline(pulumi.CustomResource):
             * [Official Documentation](https://cloud.google.com/dataflow)
 
         ## Example Usage
+
         ### Data Pipeline Pipeline
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_gcp as gcp
@@ -541,20 +543,21 @@ class Pipeline(pulumi.CustomResource):
                 schedule="* */2 * * *",
             ))
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Import
 
         Pipeline can be imported using any of these accepted formats:
 
-         * `projects/{{project}}/locations/{{region}}/pipelines/{{name}}`
+        * `projects/{{project}}/locations/{{region}}/pipelines/{{name}}`
 
-         * `{{project}}/{{region}}/{{name}}`
+        * `{{project}}/{{region}}/{{name}}`
 
-         * `{{region}}/{{name}}`
+        * `{{region}}/{{name}}`
 
-         * `{{name}}`
+        * `{{name}}`
 
-         When using the `pulumi import` command, Pipeline can be imported using one of the formats above. For example:
+        When using the `pulumi import` command, Pipeline can be imported using one of the formats above. For example:
 
         ```sh
         $ pulumi import gcp:dataflow/pipeline:Pipeline default projects/{{project}}/locations/{{region}}/pipelines/{{name}}
@@ -617,8 +620,10 @@ class Pipeline(pulumi.CustomResource):
             * [Official Documentation](https://cloud.google.com/dataflow)
 
         ## Example Usage
+
         ### Data Pipeline Pipeline
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_gcp as gcp
@@ -669,20 +674,21 @@ class Pipeline(pulumi.CustomResource):
                 schedule="* */2 * * *",
             ))
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Import
 
         Pipeline can be imported using any of these accepted formats:
 
-         * `projects/{{project}}/locations/{{region}}/pipelines/{{name}}`
+        * `projects/{{project}}/locations/{{region}}/pipelines/{{name}}`
 
-         * `{{project}}/{{region}}/{{name}}`
+        * `{{project}}/{{region}}/{{name}}`
 
-         * `{{region}}/{{name}}`
+        * `{{region}}/{{name}}`
 
-         * `{{name}}`
+        * `{{name}}`
 
-         When using the `pulumi import` command, Pipeline can be imported using one of the formats above. For example:
+        When using the `pulumi import` command, Pipeline can be imported using one of the formats above. For example:
 
         ```sh
         $ pulumi import gcp:dataflow/pipeline:Pipeline default projects/{{project}}/locations/{{region}}/pipelines/{{name}}

pulumi_gcp/dataform/repository.py

@@ -408,8 +408,10 @@ class Repository(pulumi.CustomResource):
                  __props__=None):
         """
         ## Example Usage
+
         ### Dataform Repository
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_gcp as gcp
@@ -441,8 +443,10 @@ class Repository(pulumi.CustomResource):
                 table_prefix="prefix_",
             ))
         ```
+        <!--End PulumiCodeChooser -->
         ### Dataform Repository Ssh
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_gcp as gcp
@@ -473,20 +477,21 @@ class Repository(pulumi.CustomResource):
             ),
             service_account="1234567890-compute@developer.gserviceaccount.com")
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Import
 
         Repository can be imported using any of these accepted formats:
 
-         * `projects/{{project}}/locations/{{region}}/repositories/{{name}}`
+        * `projects/{{project}}/locations/{{region}}/repositories/{{name}}`
 
-         * `{{project}}/{{region}}/{{name}}`
+        * `{{project}}/{{region}}/{{name}}`
 
-         * `{{region}}/{{name}}`
+        * `{{region}}/{{name}}`
 
-         * `{{name}}`
+        * `{{name}}`
 
-         When using the `pulumi import` command, Repository can be imported using one of the formats above. For example:
+        When using the `pulumi import` command, Repository can be imported using one of the formats above. For example:
 
         ```sh
         $ pulumi import gcp:dataform/repository:Repository default projects/{{project}}/locations/{{region}}/repositories/{{name}}
@@ -534,8 +539,10 @@ class Repository(pulumi.CustomResource):
                  opts: Optional[pulumi.ResourceOptions] = None):
         """
         ## Example Usage
+
         ### Dataform Repository
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_gcp as gcp
@@ -567,8 +574,10 @@ class Repository(pulumi.CustomResource):
                 table_prefix="prefix_",
             ))
         ```
+        <!--End PulumiCodeChooser -->
         ### Dataform Repository Ssh
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_gcp as gcp
@@ -599,20 +608,21 @@ class Repository(pulumi.CustomResource):
             ),
             service_account="1234567890-compute@developer.gserviceaccount.com")
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Import
 
         Repository can be imported using any of these accepted formats:
 
-         * `projects/{{project}}/locations/{{region}}/repositories/{{name}}`
+        * `projects/{{project}}/locations/{{region}}/repositories/{{name}}`
 
-         * `{{project}}/{{region}}/{{name}}`
+        * `{{project}}/{{region}}/{{name}}`
 
-         * `{{region}}/{{name}}`
+        * `{{region}}/{{name}}`
 
-         * `{{name}}`
+        * `{{name}}`
 
-         When using the `pulumi import` command, Repository can be imported using one of the formats above. For example:
+        When using the `pulumi import` command, Repository can be imported using one of the formats above. For example:
 
         ```sh
         $ pulumi import gcp:dataform/repository:Repository default projects/{{project}}/locations/{{region}}/repositories/{{name}}

pulumi_gcp/dataform/repository_release_config.py

@@ -338,8 +338,10 @@ class RepositoryReleaseConfig(pulumi.CustomResource):
                  __props__=None):
         """
         ## Example Usage
+
         ### Dataform Repository Release Config
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_gcp as gcp
@@ -387,20 +389,21 @@ class RepositoryReleaseConfig(pulumi.CustomResource):
                 },
             ))
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Import
 
         RepositoryReleaseConfig can be imported using any of these accepted formats:
 
-         * `projects/{{project}}/locations/{{region}}/repositories/{{repository}}/releaseConfigs/{{name}}`
+        * `projects/{{project}}/locations/{{region}}/repositories/{{repository}}/releaseConfigs/{{name}}`
 
-         * `{{project}}/{{region}}/{{repository}}/{{name}}`
+        * `{{project}}/{{region}}/{{repository}}/{{name}}`
 
-         * `{{region}}/{{repository}}/{{name}}`
+        * `{{region}}/{{repository}}/{{name}}`
 
-         * `{{repository}}/{{name}}`
+        * `{{repository}}/{{name}}`
 
-         When using the `pulumi import` command, RepositoryReleaseConfig can be imported using one of the formats above. For example:
+        When using the `pulumi import` command, RepositoryReleaseConfig can be imported using one of the formats above. For example:
 
         ```sh
         $ pulumi import gcp:dataform/repositoryReleaseConfig:RepositoryReleaseConfig default projects/{{project}}/locations/{{region}}/repositories/{{repository}}/releaseConfigs/{{name}}
@@ -442,8 +445,10 @@ class RepositoryReleaseConfig(pulumi.CustomResource):
                  opts: Optional[pulumi.ResourceOptions] = None):
         """
         ## Example Usage
+
         ### Dataform Repository Release Config
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_gcp as gcp
@@ -491,20 +496,21 @@ class RepositoryReleaseConfig(pulumi.CustomResource):
                 },
             ))
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Import
 
         RepositoryReleaseConfig can be imported using any of these accepted formats:
 
-         * `projects/{{project}}/locations/{{region}}/repositories/{{repository}}/releaseConfigs/{{name}}`
+        * `projects/{{project}}/locations/{{region}}/repositories/{{repository}}/releaseConfigs/{{name}}`
 
-         * `{{project}}/{{region}}/{{repository}}/{{name}}`
+        * `{{project}}/{{region}}/{{repository}}/{{name}}`
 
-         * `{{region}}/{{repository}}/{{name}}`
+        * `{{region}}/{{repository}}/{{name}}`
 
-         * `{{repository}}/{{name}}`
+        * `{{repository}}/{{name}}`
 
-         When using the `pulumi import` command, RepositoryReleaseConfig can be imported using one of the formats above. For example:
+        When using the `pulumi import` command, RepositoryReleaseConfig can be imported using one of the formats above. For example:
 
         ```sh
         $ pulumi import gcp:dataform/repositoryReleaseConfig:RepositoryReleaseConfig default projects/{{project}}/locations/{{region}}/repositories/{{repository}}/releaseConfigs/{{name}}

pulumi_gcp/dataform/repository_workflow_config.py

@@ -338,8 +338,10 @@ class RepositoryWorkflowConfig(pulumi.CustomResource):
                  __props__=None):
         """
         ## Example Usage
+
         ### Dataform Repository Workflow Config
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_gcp as gcp
@@ -417,20 +419,21 @@ class RepositoryWorkflowConfig(pulumi.CustomResource):
             cron_schedule="0 7 * * *",
             time_zone="America/New_York")
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Import
 
         RepositoryWorkflowConfig can be imported using any of these accepted formats:
 
-         * `projects/{{project}}/locations/{{region}}/repositories/{{repository}}/workflowConfigs/{{name}}`
+        * `projects/{{project}}/locations/{{region}}/repositories/{{repository}}/workflowConfigs/{{name}}`
 
-         * `{{project}}/{{region}}/{{repository}}/{{name}}`
+        * `{{project}}/{{region}}/{{repository}}/{{name}}`
 
-         * `{{region}}/{{repository}}/{{name}}`
+        * `{{region}}/{{repository}}/{{name}}`
 
-         * `{{repository}}/{{name}}`
+        * `{{repository}}/{{name}}`
 
-         When using the `pulumi import` command, RepositoryWorkflowConfig can be imported using one of the formats above. For example:
+        When using the `pulumi import` command, RepositoryWorkflowConfig can be imported using one of the formats above. For example:
 
         ```sh
         $ pulumi import gcp:dataform/repositoryWorkflowConfig:RepositoryWorkflowConfig default projects/{{project}}/locations/{{region}}/repositories/{{repository}}/workflowConfigs/{{name}}
@@ -472,8 +475,10 @@ class RepositoryWorkflowConfig(pulumi.CustomResource):
                  opts: Optional[pulumi.ResourceOptions] = None):
         """
         ## Example Usage
+
         ### Dataform Repository Workflow Config
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_gcp as gcp
@@ -551,20 +556,21 @@ class RepositoryWorkflowConfig(pulumi.CustomResource):
             cron_schedule="0 7 * * *",
             time_zone="America/New_York")
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Import
 
         RepositoryWorkflowConfig can be imported using any of these accepted formats:
 
-         * `projects/{{project}}/locations/{{region}}/repositories/{{repository}}/workflowConfigs/{{name}}`
+        * `projects/{{project}}/locations/{{region}}/repositories/{{repository}}/workflowConfigs/{{name}}`
 
-         * `{{project}}/{{region}}/{{repository}}/{{name}}`
+        * `{{project}}/{{region}}/{{repository}}/{{name}}`
 
-         * `{{region}}/{{repository}}/{{name}}`
+        * `{{region}}/{{repository}}/{{name}}`
 
-         * `{{repository}}/{{name}}`
+        * `{{repository}}/{{name}}`
 
-         When using the `pulumi import` command, RepositoryWorkflowConfig can be imported using one of the formats above. For example:
+        When using the `pulumi import` command, RepositoryWorkflowConfig can be imported using one of the formats above. For example:
 
         ```sh
         $ pulumi import gcp:dataform/repositoryWorkflowConfig:RepositoryWorkflowConfig default projects/{{project}}/locations/{{region}}/repositories/{{repository}}/workflowConfigs/{{name}}

pulumi_gcp/datafusion/get_instance_iam_policy.py

@@ -105,6 +105,7 @@ def get_instance_iam_policy(name: Optional[str] = None,
 
     ## example
 
+    <!--Start PulumiCodeChooser -->
     ```python
     import pulumi
     import pulumi_gcp as gcp
@@ -113,6 +114,7 @@ def get_instance_iam_policy(name: Optional[str] = None,
         region=basic_instance["region"],
         name=basic_instance["name"])
     ```
+    <!--End PulumiCodeChooser -->
 
 
     :param str name: Used to find the parent resource to bind the IAM policy to
@@ -149,6 +151,7 @@ def get_instance_iam_policy_output(name: Optional[pulumi.Input[str]] = None,
 
     ## example
 
+    <!--Start PulumiCodeChooser -->
     ```python
     import pulumi
     import pulumi_gcp as gcp
@@ -157,6 +160,7 @@ def get_instance_iam_policy_output(name: Optional[pulumi.Input[str]] = None,
         region=basic_instance["region"],
         name=basic_instance["name"])
     ```
+    <!--End PulumiCodeChooser -->
 
 
     :param str name: Used to find the parent resource to bind the IAM policy to