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

pulumi_gcp/compute/network_firewall_policy_rule.py

@@ -517,15 +517,7 @@ class NetworkFirewallPolicyRule(pulumi.CustomResource):
 
         ## Import
 
-        NetworkFirewallPolicyRule can be imported using any of these accepted formats* `projects/{{project}}/global/firewallPolicies/{{firewall_policy}}/rules/{{priority}}` * `{{project}}/{{firewall_policy}}/{{priority}}` * `{{firewall_policy}}/{{priority}}` In Terraform v1.5.0 and later, use an [`import` block](https://developer.hashicorp.com/terraform/language/import) to import NetworkFirewallPolicyRule using one of the formats above. For exampletf import {
-
-         id = "projects/{{project}}/global/firewallPolicies/{{firewall_policy}}/rules/{{priority}}"
-
-         to = google_compute_network_firewall_policy_rule.default }
-
-        ```sh
-         $ pulumi import gcp:compute/networkFirewallPolicyRule:NetworkFirewallPolicyRule When using the [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import), NetworkFirewallPolicyRule can be imported using one of the formats above. For example
-        ```
+        NetworkFirewallPolicyRule can be imported using any of these accepted formats* `projects/{{project}}/global/firewallPolicies/{{firewall_policy}}/rules/{{priority}}` * `{{project}}/{{firewall_policy}}/{{priority}}` * `{{firewall_policy}}/{{priority}}` When using the `pulumi import` command, NetworkFirewallPolicyRule can be imported using one of the formats above. For example
 
         ```sh
          $ pulumi import gcp:compute/networkFirewallPolicyRule:NetworkFirewallPolicyRule default projects/{{project}}/global/firewallPolicies/{{firewall_policy}}/rules/{{priority}}
@@ -619,15 +611,7 @@ class NetworkFirewallPolicyRule(pulumi.CustomResource):
 
         ## Import
 
-        NetworkFirewallPolicyRule can be imported using any of these accepted formats* `projects/{{project}}/global/firewallPolicies/{{firewall_policy}}/rules/{{priority}}` * `{{project}}/{{firewall_policy}}/{{priority}}` * `{{firewall_policy}}/{{priority}}` In Terraform v1.5.0 and later, use an [`import` block](https://developer.hashicorp.com/terraform/language/import) to import NetworkFirewallPolicyRule using one of the formats above. For exampletf import {
-
-         id = "projects/{{project}}/global/firewallPolicies/{{firewall_policy}}/rules/{{priority}}"
-
-         to = google_compute_network_firewall_policy_rule.default }
-
-        ```sh
-         $ pulumi import gcp:compute/networkFirewallPolicyRule:NetworkFirewallPolicyRule When using the [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import), NetworkFirewallPolicyRule can be imported using one of the formats above. For example
-        ```
+        NetworkFirewallPolicyRule can be imported using any of these accepted formats* `projects/{{project}}/global/firewallPolicies/{{firewall_policy}}/rules/{{priority}}` * `{{project}}/{{firewall_policy}}/{{priority}}` * `{{firewall_policy}}/{{priority}}` When using the `pulumi import` command, NetworkFirewallPolicyRule can be imported using one of the formats above. For example
 
         ```sh
          $ pulumi import gcp:compute/networkFirewallPolicyRule:NetworkFirewallPolicyRule default projects/{{project}}/global/firewallPolicies/{{firewall_policy}}/rules/{{priority}}

pulumi_gcp/compute/network_peering.py

@@ -362,15 +362,7 @@ class NetworkPeering(pulumi.CustomResource):
 
         ## Import
 
-        VPC network peerings can be imported using the name and project of the primary network the peering exists in and the name of the network peering * `{{project_id}}/{{network_id}}/{{peering_id}}` In Terraform v1.5.0 and later, use an [`import` block](https://developer.hashicorp.com/terraform/language/import) to import VPC network peerings using one of the formats above. For exampletf import {
-
-         id = "{{project_id}}/{{network_id}}/{{peering_id}}"
-
-         to = google_compute_network_peering.default }
-
-        ```sh
-         $ pulumi import gcp:compute/networkPeering:NetworkPeering When using the [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import), VPC network peerings can be imported using one of the formats above. For example
-        ```
+        VPC network peerings can be imported using the name and project of the primary network the peering exists in and the name of the network peering * `{{project_id}}/{{network_id}}/{{peering_id}}` When using the `pulumi import` command, VPC network peerings can be imported using one of the formats above. For example
 
         ```sh
          $ pulumi import gcp:compute/networkPeering:NetworkPeering default {{project_id}}/{{network_id}}/{{peering_id}}
@@ -423,15 +415,7 @@ class NetworkPeering(pulumi.CustomResource):
 
         ## Import
 
-        VPC network peerings can be imported using the name and project of the primary network the peering exists in and the name of the network peering * `{{project_id}}/{{network_id}}/{{peering_id}}` In Terraform v1.5.0 and later, use an [`import` block](https://developer.hashicorp.com/terraform/language/import) to import VPC network peerings using one of the formats above. For exampletf import {
-
-         id = "{{project_id}}/{{network_id}}/{{peering_id}}"
-
-         to = google_compute_network_peering.default }
-
-        ```sh
-         $ pulumi import gcp:compute/networkPeering:NetworkPeering When using the [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import), VPC network peerings can be imported using one of the formats above. For example
-        ```
+        VPC network peerings can be imported using the name and project of the primary network the peering exists in and the name of the network peering * `{{project_id}}/{{network_id}}/{{peering_id}}` When using the `pulumi import` command, VPC network peerings can be imported using one of the formats above. For example
 
         ```sh
          $ pulumi import gcp:compute/networkPeering:NetworkPeering default {{project_id}}/{{network_id}}/{{peering_id}}

pulumi_gcp/compute/network_peering_routes_config.py

@@ -292,15 +292,7 @@ class NetworkPeeringRoutesConfig(pulumi.CustomResource):
 
         ## Import
 
-        NetworkPeeringRoutesConfig can be imported using any of these accepted formats* `projects/{{project}}/global/networks/{{network}}/networkPeerings/{{peering}}` * `{{project}}/{{network}}/{{peering}}` * `{{network}}/{{peering}}` In Terraform v1.5.0 and later, use an [`import` block](https://developer.hashicorp.com/terraform/language/import) to import NetworkPeeringRoutesConfig using one of the formats above. For exampletf import {
-
-         id = "projects/{{project}}/global/networks/{{network}}/networkPeerings/{{peering}}"
-
-         to = google_compute_network_peering_routes_config.default }
-
-        ```sh
-         $ pulumi import gcp:compute/networkPeeringRoutesConfig:NetworkPeeringRoutesConfig When using the [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import), NetworkPeeringRoutesConfig can be imported using one of the formats above. For example
-        ```
+        NetworkPeeringRoutesConfig can be imported using any of these accepted formats* `projects/{{project}}/global/networks/{{network}}/networkPeerings/{{peering}}` * `{{project}}/{{network}}/{{peering}}` * `{{network}}/{{peering}}` When using the `pulumi import` command, NetworkPeeringRoutesConfig can be imported using one of the formats above. For example
 
         ```sh
          $ pulumi import gcp:compute/networkPeeringRoutesConfig:NetworkPeeringRoutesConfig default projects/{{project}}/global/networks/{{network}}/networkPeerings/{{peering}}
@@ -414,15 +406,7 @@ class NetworkPeeringRoutesConfig(pulumi.CustomResource):
 
         ## Import
 
-        NetworkPeeringRoutesConfig can be imported using any of these accepted formats* `projects/{{project}}/global/networks/{{network}}/networkPeerings/{{peering}}` * `{{project}}/{{network}}/{{peering}}` * `{{network}}/{{peering}}` In Terraform v1.5.0 and later, use an [`import` block](https://developer.hashicorp.com/terraform/language/import) to import NetworkPeeringRoutesConfig using one of the formats above. For exampletf import {
-
-         id = "projects/{{project}}/global/networks/{{network}}/networkPeerings/{{peering}}"
-
-         to = google_compute_network_peering_routes_config.default }
-
-        ```sh
-         $ pulumi import gcp:compute/networkPeeringRoutesConfig:NetworkPeeringRoutesConfig When using the [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import), NetworkPeeringRoutesConfig can be imported using one of the formats above. For example
-        ```
+        NetworkPeeringRoutesConfig can be imported using any of these accepted formats* `projects/{{project}}/global/networks/{{network}}/networkPeerings/{{peering}}` * `{{project}}/{{network}}/{{peering}}` * `{{network}}/{{peering}}` When using the `pulumi import` command, NetworkPeeringRoutesConfig can be imported using one of the formats above. For example
 
         ```sh
          $ pulumi import gcp:compute/networkPeeringRoutesConfig:NetworkPeeringRoutesConfig default projects/{{project}}/global/networks/{{network}}/networkPeerings/{{peering}}

pulumi_gcp/compute/node_group.py

@@ -39,11 +39,10 @@ class NodeGroupArgs:
                Structure is documented below.
         :param pulumi.Input[str] description: An optional textual description of the resource.
         :param pulumi.Input[int] initial_size: The initial number of nodes in the node group. One of `initial_size` or `autoscaling_policy` must be configured on resource creation.
-        :param pulumi.Input[str] maintenance_interval: Specifies the frequency of planned maintenance events. Set to one of the following: - AS_NEEDED: Hosts are eligible to
-               receive infrastructure and hypervisor updates as they become available. - RECURRENT: Hosts receive planned
-               infrastructure and hypervisor updates on a periodic basis, but not more frequently than every 28 days. This minimizes
-               the number of planned maintenance operations on individual hosts and reduces the frequency of disruptions, both live
-               migrations and terminations, on individual VMs. Possible values: ["AS_NEEDED", "RECURRENT"]
+        :param pulumi.Input[str] maintenance_interval: Specifies the frequency of planned maintenance events. Set to one of the following:
+               - AS_NEEDED: Hosts are eligible to receive infrastructure and hypervisor updates as they become available.
+               - RECURRENT: Hosts receive planned infrastructure and hypervisor updates on a periodic basis, but not more frequently than every 28 days. This minimizes the number of planned maintenance operations on individual hosts and reduces the frequency of disruptions, both live migrations and terminations, on individual VMs.
+               Possible values are: `AS_NEEDED`, `RECURRENT`.
         :param pulumi.Input[str] maintenance_policy: Specifies how to handle instances when a node in the group undergoes maintenance. Set to one of: DEFAULT, RESTART_IN_PLACE, or MIGRATE_WITHIN_NODE_GROUP. The default value is DEFAULT.
         :param pulumi.Input['NodeGroupMaintenanceWindowArgs'] maintenance_window: contains properties for the timeframe of maintenance
                Structure is documented below.
@@ -134,11 +133,10 @@ class NodeGroupArgs:
     @pulumi.getter(name="maintenanceInterval")
     def maintenance_interval(self) -> Optional[pulumi.Input[str]]:
         """
-        Specifies the frequency of planned maintenance events. Set to one of the following: - AS_NEEDED: Hosts are eligible to
-        receive infrastructure and hypervisor updates as they become available. - RECURRENT: Hosts receive planned
-        infrastructure and hypervisor updates on a periodic basis, but not more frequently than every 28 days. This minimizes
-        the number of planned maintenance operations on individual hosts and reduces the frequency of disruptions, both live
-        migrations and terminations, on individual VMs. Possible values: ["AS_NEEDED", "RECURRENT"]
+        Specifies the frequency of planned maintenance events. Set to one of the following:
+        - AS_NEEDED: Hosts are eligible to receive infrastructure and hypervisor updates as they become available.
+        - RECURRENT: Hosts receive planned infrastructure and hypervisor updates on a periodic basis, but not more frequently than every 28 days. This minimizes the number of planned maintenance operations on individual hosts and reduces the frequency of disruptions, both live migrations and terminations, on individual VMs.
+        Possible values are: `AS_NEEDED`, `RECURRENT`.
         """
         return pulumi.get(self, "maintenance_interval")
 
@@ -248,11 +246,10 @@ class _NodeGroupState:
         :param pulumi.Input[str] creation_timestamp: Creation timestamp in RFC3339 text format.
         :param pulumi.Input[str] description: An optional textual description of the resource.
         :param pulumi.Input[int] initial_size: The initial number of nodes in the node group. One of `initial_size` or `autoscaling_policy` must be configured on resource creation.
-        :param pulumi.Input[str] maintenance_interval: Specifies the frequency of planned maintenance events. Set to one of the following: - AS_NEEDED: Hosts are eligible to
-               receive infrastructure and hypervisor updates as they become available. - RECURRENT: Hosts receive planned
-               infrastructure and hypervisor updates on a periodic basis, but not more frequently than every 28 days. This minimizes
-               the number of planned maintenance operations on individual hosts and reduces the frequency of disruptions, both live
-               migrations and terminations, on individual VMs. Possible values: ["AS_NEEDED", "RECURRENT"]
+        :param pulumi.Input[str] maintenance_interval: Specifies the frequency of planned maintenance events. Set to one of the following:
+               - AS_NEEDED: Hosts are eligible to receive infrastructure and hypervisor updates as they become available.
+               - RECURRENT: Hosts receive planned infrastructure and hypervisor updates on a periodic basis, but not more frequently than every 28 days. This minimizes the number of planned maintenance operations on individual hosts and reduces the frequency of disruptions, both live migrations and terminations, on individual VMs.
+               Possible values are: `AS_NEEDED`, `RECURRENT`.
         :param pulumi.Input[str] maintenance_policy: Specifies how to handle instances when a node in the group undergoes maintenance. Set to one of: DEFAULT, RESTART_IN_PLACE, or MIGRATE_WITHIN_NODE_GROUP. The default value is DEFAULT.
         :param pulumi.Input['NodeGroupMaintenanceWindowArgs'] maintenance_window: contains properties for the timeframe of maintenance
                Structure is documented below.
@@ -353,11 +350,10 @@ class _NodeGroupState:
     @pulumi.getter(name="maintenanceInterval")
     def maintenance_interval(self) -> Optional[pulumi.Input[str]]:
         """
-        Specifies the frequency of planned maintenance events. Set to one of the following: - AS_NEEDED: Hosts are eligible to
-        receive infrastructure and hypervisor updates as they become available. - RECURRENT: Hosts receive planned
-        infrastructure and hypervisor updates on a periodic basis, but not more frequently than every 28 days. This minimizes
-        the number of planned maintenance operations on individual hosts and reduces the frequency of disruptions, both live
-        migrations and terminations, on individual VMs. Possible values: ["AS_NEEDED", "RECURRENT"]
+        Specifies the frequency of planned maintenance events. Set to one of the following:
+        - AS_NEEDED: Hosts are eligible to receive infrastructure and hypervisor updates as they become available.
+        - RECURRENT: Hosts receive planned infrastructure and hypervisor updates on a periodic basis, but not more frequently than every 28 days. This minimizes the number of planned maintenance operations on individual hosts and reduces the frequency of disruptions, both live migrations and terminations, on individual VMs.
+        Possible values are: `AS_NEEDED`, `RECURRENT`.
         """
         return pulumi.get(self, "maintenance_interval")
 
@@ -595,15 +591,7 @@ class NodeGroup(pulumi.CustomResource):
 
         ## Import
 
-        NodeGroup can be imported using any of these accepted formats* `projects/{{project}}/zones/{{zone}}/nodeGroups/{{name}}` * `{{project}}/{{zone}}/{{name}}` * `{{zone}}/{{name}}` * `{{name}}` In Terraform v1.5.0 and later, use an [`import` block](https://developer.hashicorp.com/terraform/language/import) to import NodeGroup using one of the formats above. For exampletf import {
-
-         id = "projects/{{project}}/zones/{{zone}}/nodeGroups/{{name}}"
-
-         to = google_compute_node_group.default }
-
-        ```sh
-         $ pulumi import gcp:compute/nodeGroup:NodeGroup When using the [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import), NodeGroup can be imported using one of the formats above. For example
-        ```
+        NodeGroup can be imported using any of these accepted formats* `projects/{{project}}/zones/{{zone}}/nodeGroups/{{name}}` * `{{project}}/{{zone}}/{{name}}` * `{{zone}}/{{name}}` * `{{name}}` When using the `pulumi import` command, NodeGroup can be imported using one of the formats above. For example
 
         ```sh
          $ pulumi import gcp:compute/nodeGroup:NodeGroup default projects/{{project}}/zones/{{zone}}/nodeGroups/{{name}}
@@ -629,11 +617,10 @@ class NodeGroup(pulumi.CustomResource):
                Structure is documented below.
         :param pulumi.Input[str] description: An optional textual description of the resource.
         :param pulumi.Input[int] initial_size: The initial number of nodes in the node group. One of `initial_size` or `autoscaling_policy` must be configured on resource creation.
-        :param pulumi.Input[str] maintenance_interval: Specifies the frequency of planned maintenance events. Set to one of the following: - AS_NEEDED: Hosts are eligible to
-               receive infrastructure and hypervisor updates as they become available. - RECURRENT: Hosts receive planned
-               infrastructure and hypervisor updates on a periodic basis, but not more frequently than every 28 days. This minimizes
-               the number of planned maintenance operations on individual hosts and reduces the frequency of disruptions, both live
-               migrations and terminations, on individual VMs. Possible values: ["AS_NEEDED", "RECURRENT"]
+        :param pulumi.Input[str] maintenance_interval: Specifies the frequency of planned maintenance events. Set to one of the following:
+               - AS_NEEDED: Hosts are eligible to receive infrastructure and hypervisor updates as they become available.
+               - RECURRENT: Hosts receive planned infrastructure and hypervisor updates on a periodic basis, but not more frequently than every 28 days. This minimizes the number of planned maintenance operations on individual hosts and reduces the frequency of disruptions, both live migrations and terminations, on individual VMs.
+               Possible values are: `AS_NEEDED`, `RECURRENT`.
         :param pulumi.Input[str] maintenance_policy: Specifies how to handle instances when a node in the group undergoes maintenance. Set to one of: DEFAULT, RESTART_IN_PLACE, or MIGRATE_WITHIN_NODE_GROUP. The default value is DEFAULT.
         :param pulumi.Input[pulumi.InputType['NodeGroupMaintenanceWindowArgs']] maintenance_window: contains properties for the timeframe of maintenance
                Structure is documented below.
@@ -752,15 +739,7 @@ class NodeGroup(pulumi.CustomResource):
 
         ## Import
 
-        NodeGroup can be imported using any of these accepted formats* `projects/{{project}}/zones/{{zone}}/nodeGroups/{{name}}` * `{{project}}/{{zone}}/{{name}}` * `{{zone}}/{{name}}` * `{{name}}` In Terraform v1.5.0 and later, use an [`import` block](https://developer.hashicorp.com/terraform/language/import) to import NodeGroup using one of the formats above. For exampletf import {
-
-         id = "projects/{{project}}/zones/{{zone}}/nodeGroups/{{name}}"
-
-         to = google_compute_node_group.default }
-
-        ```sh
-         $ pulumi import gcp:compute/nodeGroup:NodeGroup When using the [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import), NodeGroup can be imported using one of the formats above. For example
-        ```
+        NodeGroup can be imported using any of these accepted formats* `projects/{{project}}/zones/{{zone}}/nodeGroups/{{name}}` * `{{project}}/{{zone}}/{{name}}` * `{{zone}}/{{name}}` * `{{name}}` When using the `pulumi import` command, NodeGroup can be imported using one of the formats above. For example
 
         ```sh
          $ pulumi import gcp:compute/nodeGroup:NodeGroup default projects/{{project}}/zones/{{zone}}/nodeGroups/{{name}}
@@ -867,11 +846,10 @@ class NodeGroup(pulumi.CustomResource):
         :param pulumi.Input[str] creation_timestamp: Creation timestamp in RFC3339 text format.
         :param pulumi.Input[str] description: An optional textual description of the resource.
         :param pulumi.Input[int] initial_size: The initial number of nodes in the node group. One of `initial_size` or `autoscaling_policy` must be configured on resource creation.
-        :param pulumi.Input[str] maintenance_interval: Specifies the frequency of planned maintenance events. Set to one of the following: - AS_NEEDED: Hosts are eligible to
-               receive infrastructure and hypervisor updates as they become available. - RECURRENT: Hosts receive planned
-               infrastructure and hypervisor updates on a periodic basis, but not more frequently than every 28 days. This minimizes
-               the number of planned maintenance operations on individual hosts and reduces the frequency of disruptions, both live
-               migrations and terminations, on individual VMs. Possible values: ["AS_NEEDED", "RECURRENT"]
+        :param pulumi.Input[str] maintenance_interval: Specifies the frequency of planned maintenance events. Set to one of the following:
+               - AS_NEEDED: Hosts are eligible to receive infrastructure and hypervisor updates as they become available.
+               - RECURRENT: Hosts receive planned infrastructure and hypervisor updates on a periodic basis, but not more frequently than every 28 days. This minimizes the number of planned maintenance operations on individual hosts and reduces the frequency of disruptions, both live migrations and terminations, on individual VMs.
+               Possible values are: `AS_NEEDED`, `RECURRENT`.
         :param pulumi.Input[str] maintenance_policy: Specifies how to handle instances when a node in the group undergoes maintenance. Set to one of: DEFAULT, RESTART_IN_PLACE, or MIGRATE_WITHIN_NODE_GROUP. The default value is DEFAULT.
         :param pulumi.Input[pulumi.InputType['NodeGroupMaintenanceWindowArgs']] maintenance_window: contains properties for the timeframe of maintenance
                Structure is documented below.
@@ -947,11 +925,10 @@ class NodeGroup(pulumi.CustomResource):
     @pulumi.getter(name="maintenanceInterval")
     def maintenance_interval(self) -> pulumi.Output[str]:
         """
-        Specifies the frequency of planned maintenance events. Set to one of the following: - AS_NEEDED: Hosts are eligible to
-        receive infrastructure and hypervisor updates as they become available. - RECURRENT: Hosts receive planned
-        infrastructure and hypervisor updates on a periodic basis, but not more frequently than every 28 days. This minimizes
-        the number of planned maintenance operations on individual hosts and reduces the frequency of disruptions, both live
-        migrations and terminations, on individual VMs. Possible values: ["AS_NEEDED", "RECURRENT"]
+        Specifies the frequency of planned maintenance events. Set to one of the following:
+        - AS_NEEDED: Hosts are eligible to receive infrastructure and hypervisor updates as they become available.
+        - RECURRENT: Hosts receive planned infrastructure and hypervisor updates on a periodic basis, but not more frequently than every 28 days. This minimizes the number of planned maintenance operations on individual hosts and reduces the frequency of disruptions, both live migrations and terminations, on individual VMs.
+        Possible values are: `AS_NEEDED`, `RECURRENT`.
         """
         return pulumi.get(self, "maintenance_interval")
 

pulumi_gcp/compute/node_template.py

@@ -454,15 +454,7 @@ class NodeTemplate(pulumi.CustomResource):
 
         ## Import
 
-        NodeTemplate can be imported using any of these accepted formats* `projects/{{project}}/regions/{{region}}/nodeTemplates/{{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 NodeTemplate using one of the formats above. For exampletf import {
-
-         id = "projects/{{project}}/regions/{{region}}/nodeTemplates/{{name}}"
-
-         to = google_compute_node_template.default }
-
-        ```sh
-         $ pulumi import gcp:compute/nodeTemplate:NodeTemplate When using the [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import), NodeTemplate can be imported using one of the formats above. For example
-        ```
+        NodeTemplate can be imported using any of these accepted formats* `projects/{{project}}/regions/{{region}}/nodeTemplates/{{name}}` * `{{project}}/{{region}}/{{name}}` * `{{region}}/{{name}}` * `{{name}}` When using the `pulumi import` command, NodeTemplate can be imported using one of the formats above. For example
 
         ```sh
          $ pulumi import gcp:compute/nodeTemplate:NodeTemplate default projects/{{project}}/regions/{{region}}/nodeTemplates/{{name}}
@@ -552,15 +544,7 @@ class NodeTemplate(pulumi.CustomResource):
 
         ## Import
 
-        NodeTemplate can be imported using any of these accepted formats* `projects/{{project}}/regions/{{region}}/nodeTemplates/{{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 NodeTemplate using one of the formats above. For exampletf import {
-
-         id = "projects/{{project}}/regions/{{region}}/nodeTemplates/{{name}}"
-
-         to = google_compute_node_template.default }
-
-        ```sh
-         $ pulumi import gcp:compute/nodeTemplate:NodeTemplate When using the [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import), NodeTemplate can be imported using one of the formats above. For example
-        ```
+        NodeTemplate can be imported using any of these accepted formats* `projects/{{project}}/regions/{{region}}/nodeTemplates/{{name}}` * `{{project}}/{{region}}/{{name}}` * `{{region}}/{{name}}` * `{{name}}` When using the `pulumi import` command, NodeTemplate can be imported using one of the formats above. For example
 
         ```sh
          $ pulumi import gcp:compute/nodeTemplate:NodeTemplate default projects/{{project}}/regions/{{region}}/nodeTemplates/{{name}}

pulumi_gcp/compute/organization_security_policy.py

@@ -253,15 +253,7 @@ class OrganizationSecurityPolicy(pulumi.CustomResource):
 
         ## Import
 
-        OrganizationSecurityPolicy can be imported using any of these accepted formats* `locations/global/securityPolicies/{{policy_id}}` * `{{policy_id}}` In Terraform v1.5.0 and later, use an [`import` block](https://developer.hashicorp.com/terraform/language/import) to import OrganizationSecurityPolicy using one of the formats above. For exampletf import {
-
-         id = "locations/global/securityPolicies/{{policy_id}}"
-
-         to = google_compute_organization_security_policy.default }
-
-        ```sh
-         $ pulumi import gcp:compute/organizationSecurityPolicy:OrganizationSecurityPolicy When using the [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import), OrganizationSecurityPolicy can be imported using one of the formats above. For example
-        ```
+        OrganizationSecurityPolicy can be imported using any of these accepted formats* `locations/global/securityPolicies/{{policy_id}}` * `{{policy_id}}` When using the `pulumi import` command, OrganizationSecurityPolicy can be imported using one of the formats above. For example
 
         ```sh
          $ pulumi import gcp:compute/organizationSecurityPolicy:OrganizationSecurityPolicy default locations/global/securityPolicies/{{policy_id}}
@@ -316,15 +308,7 @@ class OrganizationSecurityPolicy(pulumi.CustomResource):
 
         ## Import
 
-        OrganizationSecurityPolicy can be imported using any of these accepted formats* `locations/global/securityPolicies/{{policy_id}}` * `{{policy_id}}` In Terraform v1.5.0 and later, use an [`import` block](https://developer.hashicorp.com/terraform/language/import) to import OrganizationSecurityPolicy using one of the formats above. For exampletf import {
-
-         id = "locations/global/securityPolicies/{{policy_id}}"
-
-         to = google_compute_organization_security_policy.default }
-
-        ```sh
-         $ pulumi import gcp:compute/organizationSecurityPolicy:OrganizationSecurityPolicy When using the [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import), OrganizationSecurityPolicy can be imported using one of the formats above. For example
-        ```
+        OrganizationSecurityPolicy can be imported using any of these accepted formats* `locations/global/securityPolicies/{{policy_id}}` * `{{policy_id}}` When using the `pulumi import` command, OrganizationSecurityPolicy can be imported using one of the formats above. For example
 
         ```sh
          $ pulumi import gcp:compute/organizationSecurityPolicy:OrganizationSecurityPolicy default locations/global/securityPolicies/{{policy_id}}

pulumi_gcp/compute/organization_security_policy_association.py

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

pulumi_gcp/compute/organization_security_policy_rule.py

@@ -453,15 +453,7 @@ class OrganizationSecurityPolicyRule(pulumi.CustomResource):
 
         ## Import
 
-        OrganizationSecurityPolicyRule can be imported using any of these accepted formats* `{{policy_id}}/priority/{{priority}}` In Terraform v1.5.0 and later, use an [`import` block](https://developer.hashicorp.com/terraform/language/import) to import OrganizationSecurityPolicyRule using one of the formats above. For exampletf import {
-
-         id = "{{policy_id}}/priority/{{priority}}"
-
-         to = google_compute_organization_security_policy_rule.default }
-
-        ```sh
-         $ pulumi import gcp:compute/organizationSecurityPolicyRule:OrganizationSecurityPolicyRule When using the [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import), OrganizationSecurityPolicyRule can be imported using one of the formats above. For example
-        ```
+        OrganizationSecurityPolicyRule can be imported using any of these accepted formats* `{{policy_id}}/priority/{{priority}}` When using the `pulumi import` command, OrganizationSecurityPolicyRule can be imported using one of the formats above. For example
 
         ```sh
          $ pulumi import gcp:compute/organizationSecurityPolicyRule:OrganizationSecurityPolicyRule default {{policy_id}}/priority/{{priority}}
@@ -545,15 +537,7 @@ class OrganizationSecurityPolicyRule(pulumi.CustomResource):
 
         ## Import
 
-        OrganizationSecurityPolicyRule can be imported using any of these accepted formats* `{{policy_id}}/priority/{{priority}}` In Terraform v1.5.0 and later, use an [`import` block](https://developer.hashicorp.com/terraform/language/import) to import OrganizationSecurityPolicyRule using one of the formats above. For exampletf import {
-
-         id = "{{policy_id}}/priority/{{priority}}"
-
-         to = google_compute_organization_security_policy_rule.default }
-
-        ```sh
-         $ pulumi import gcp:compute/organizationSecurityPolicyRule:OrganizationSecurityPolicyRule When using the [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import), OrganizationSecurityPolicyRule can be imported using one of the formats above. For example
-        ```
+        OrganizationSecurityPolicyRule can be imported using any of these accepted formats* `{{policy_id}}/priority/{{priority}}` When using the `pulumi import` command, OrganizationSecurityPolicyRule can be imported using one of the formats above. For example
 
         ```sh
          $ pulumi import gcp:compute/organizationSecurityPolicyRule:OrganizationSecurityPolicyRule default {{policy_id}}/priority/{{priority}}