pulumi-newrelic 5.20.0a1709365820__py3-none-any.whl → 5.21.0__py3-none-any.whl

pulumi_newrelic/alert_condition.py

@@ -46,9 +46,11 @@ class AlertConditionArgs:
                
                > **NOTE:** The `user_defined_value_function` can have `rate` or `percent` only when the `type` is `mobile_metric`.
                
+               <!--Start PulumiCodeChooser -->
                ```python
                import pulumi
                ```
+               <!--End PulumiCodeChooser -->
         :param pulumi.Input[int] violation_close_timer: Automatically close instance-based incidents, including JVM health metric incidents, after the number of hours specified. Must be between 1 and 720 hours. Must be specified in the following two cases, to prevent drift:
                * when `type` = `apm_app_metric` and `condition_scope` = `instance`
                * when `type` = `apm_jvm_metric`
@@ -215,9 +217,11 @@ class AlertConditionArgs:
 
         > **NOTE:** The `user_defined_value_function` can have `rate` or `percent` only when the `type` is `mobile_metric`.
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         ```
+        <!--End PulumiCodeChooser -->
         """
         return pulumi.get(self, "user_defined_value_function")
 
@@ -275,9 +279,11 @@ class _AlertConditionState:
                
                > **NOTE:** The `user_defined_value_function` can have `rate` or `percent` only when the `type` is `mobile_metric`.
                
+               <!--Start PulumiCodeChooser -->
                ```python
                import pulumi
                ```
+               <!--End PulumiCodeChooser -->
         :param pulumi.Input[int] violation_close_timer: Automatically close instance-based incidents, including JVM health metric incidents, after the number of hours specified. Must be between 1 and 720 hours. Must be specified in the following two cases, to prevent drift:
                * when `type` = `apm_app_metric` and `condition_scope` = `instance`
                * when `type` = `apm_jvm_metric`
@@ -463,9 +469,11 @@ class _AlertConditionState:
 
         > **NOTE:** The `user_defined_value_function` can have `rate` or `percent` only when the `type` is `mobile_metric`.
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         ```
+        <!--End PulumiCodeChooser -->
         """
         return pulumi.get(self, "user_defined_value_function")
 
@@ -514,6 +522,7 @@ class AlertCondition(pulumi.CustomResource):
 
         ## Example Usage
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -537,6 +546,8 @@ class AlertCondition(pulumi.CustomResource):
                 time_function="all",
             )])
         ```
+        <!--End PulumiCodeChooser -->
+
         ## Terms
 
         The `term` mapping supports the following arguments:
@@ -551,6 +562,7 @@ class AlertCondition(pulumi.CustomResource):
 
         Manage alert condition tags with `EntityTags`. For up-to-date documentation about the tagging resource, please check EntityTags
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -587,13 +599,14 @@ class AlertCondition(pulumi.CustomResource):
                 ),
             ])
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Import
 
         Alert conditions can be imported using notation `alert_policy_id:alert_condition_id`, e.g.
 
         ```sh
-         $ pulumi import newrelic:index/alertCondition:AlertCondition main 123456:6789012345
+        $ pulumi import newrelic:index/alertCondition:AlertCondition main 123456:6789012345
         ```
 
         :param str resource_name: The name of the resource.
@@ -613,9 +626,11 @@ class AlertCondition(pulumi.CustomResource):
                
                > **NOTE:** The `user_defined_value_function` can have `rate` or `percent` only when the `type` is `mobile_metric`.
                
+               <!--Start PulumiCodeChooser -->
                ```python
                import pulumi
                ```
+               <!--End PulumiCodeChooser -->
         :param pulumi.Input[int] violation_close_timer: Automatically close instance-based incidents, including JVM health metric incidents, after the number of hours specified. Must be between 1 and 720 hours. Must be specified in the following two cases, to prevent drift:
                * when `type` = `apm_app_metric` and `condition_scope` = `instance`
                * when `type` = `apm_jvm_metric`
@@ -633,6 +648,7 @@ class AlertCondition(pulumi.CustomResource):
 
         ## Example Usage
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -656,6 +672,8 @@ class AlertCondition(pulumi.CustomResource):
                 time_function="all",
             )])
         ```
+        <!--End PulumiCodeChooser -->
+
         ## Terms
 
         The `term` mapping supports the following arguments:
@@ -670,6 +688,7 @@ class AlertCondition(pulumi.CustomResource):
 
         Manage alert condition tags with `EntityTags`. For up-to-date documentation about the tagging resource, please check EntityTags
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -706,13 +725,14 @@ class AlertCondition(pulumi.CustomResource):
                 ),
             ])
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Import
 
         Alert conditions can be imported using notation `alert_policy_id:alert_condition_id`, e.g.
 
         ```sh
-         $ pulumi import newrelic:index/alertCondition:AlertCondition main 123456:6789012345
+        $ pulumi import newrelic:index/alertCondition:AlertCondition main 123456:6789012345
         ```
 
         :param str resource_name: The name of the resource.
@@ -823,9 +843,11 @@ class AlertCondition(pulumi.CustomResource):
                
                > **NOTE:** The `user_defined_value_function` can have `rate` or `percent` only when the `type` is `mobile_metric`.
                
+               <!--Start PulumiCodeChooser -->
                ```python
                import pulumi
                ```
+               <!--End PulumiCodeChooser -->
         :param pulumi.Input[int] violation_close_timer: Automatically close instance-based incidents, including JVM health metric incidents, after the number of hours specified. Must be between 1 and 720 hours. Must be specified in the following two cases, to prevent drift:
                * when `type` = `apm_app_metric` and `condition_scope` = `instance`
                * when `type` = `apm_jvm_metric`
@@ -954,9 +976,11 @@ class AlertCondition(pulumi.CustomResource):
 
         > **NOTE:** The `user_defined_value_function` can have `rate` or `percent` only when the `type` is `mobile_metric`.
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         ```
+        <!--End PulumiCodeChooser -->
         """
         return pulumi.get(self, "user_defined_value_function")
 

pulumi_newrelic/alert_muting_rule.py

@@ -234,6 +234,7 @@ class AlertMutingRule(pulumi.CustomResource):
         """
         ## Example Usage
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -269,13 +270,14 @@ class AlertMutingRule(pulumi.CustomResource):
                 ],
             ))
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Import
 
         Alert conditions can be imported using a composite ID of `<account_id>:<muting_rule_id>`, e.g.
 
         ```sh
-         $ pulumi import newrelic:index/alertMutingRule:AlertMutingRule foo 538291:6789035
+        $ pulumi import newrelic:index/alertMutingRule:AlertMutingRule foo 538291:6789035
         ```
 
         :param str resource_name: The name of the resource.
@@ -296,6 +298,7 @@ class AlertMutingRule(pulumi.CustomResource):
         """
         ## Example Usage
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -331,13 +334,14 @@ class AlertMutingRule(pulumi.CustomResource):
                 ],
             ))
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Import
 
         Alert conditions can be imported using a composite ID of `<account_id>:<muting_rule_id>`, e.g.
 
         ```sh
-         $ pulumi import newrelic:index/alertMutingRule:AlertMutingRule foo 538291:6789035
+        $ pulumi import newrelic:index/alertMutingRule:AlertMutingRule foo 538291:6789035
         ```
 
         :param str resource_name: The name of the resource.

pulumi_newrelic/alert_policy.py

@@ -181,16 +181,34 @@ class AlertPolicy(pulumi.CustomResource):
         Use this resource to create and manage New Relic alert policies.
 
         ## Example Usage
+
         ### Basic Usage
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
 
         foo = newrelic.AlertPolicy("foo", incident_preference="PER_POLICY")
         ```
+        <!--End PulumiCodeChooser -->
+
         ### Provision multiple notification channels and add those channels to a policy
 
+        The following arguments are supported:
+
+          * `name` - (Required) The name of the policy.
+          * `incident_preference` - (Optional) The rollup strategy for the policy, which can have one of the following values (the default value is `PER_POLICY`):
+            * `PER_POLICY` - This sets the incident grouping preference of the policy to **One issue per policy**. Refer to [this page](https://docs.newrelic.com/docs/alerts-applied-intelligence/new-relic-alerts/alert-policies/specify-when-alerts-create-incidents/#preference-policy) for more details on this incident grouping preference.
+            * `PER_CONDITION` - This sets the incident grouping preference of the policy to **One issue per condition**. Refer to [this page](https://docs.newrelic.com/docs/alerts-applied-intelligence/new-relic-alerts/alert-policies/specify-when-alerts-create-incidents/#preference-condition) for more details on this incident grouping preference.
+            * `PER_CONDITION_AND_TARGET` - This sets the incident grouping preference of the policy to **One issue per condition and signal**. Refer to [this page](https://docs.newrelic.com/docs/alerts-applied-intelligence/new-relic-alerts/alert-policies/specify-when-alerts-create-incidents/#preference-signal) for more details on this incident grouping preference.
+          * `channel_ids` - (Optional) **DEPRECATED** The `channel_ids` argument is deprecated and will be removed in the next major release of the provider. An array of channel IDs (integers) to assign to the policy. Adding or removing channel IDs from this array will result in a new alert policy resource being created and the old one being destroyed. Also note that channel IDs _cannot_ be imported via `pulumi import` (see Import for info).
+          * `account_id` - (Optional) The New Relic account ID to operate on.  This allows the user to override the `account_id` attribute set on the provider. Defaults to the environment variable `NEW_RELIC_ACCOUNT_ID`.
+
+        ## Additional Examples
+
+        ##### Provision multiple notification channels and add those channels to a policy
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -217,7 +235,10 @@ class AlertPolicy(pulumi.CustomResource):
                 email_channel.id,
             ])
         ```
+        <!--End PulumiCodeChooser -->
+
         ### Reference existing notification channels and add those channel to a policy
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -232,6 +253,7 @@ class AlertPolicy(pulumi.CustomResource):
                 email_channel.id,
             ])
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Import
 
@@ -240,9 +262,9 @@ class AlertPolicy(pulumi.CustomResource):
         Example import:
 
         ```sh
-         $ pulumi import newrelic:index/alertPolicy:AlertPolicy foo 23423556:4593020
+        $ pulumi import newrelic:index/alertPolicy:AlertPolicy foo 23423556:4593020
         ```
-         Please note that channel IDs (`channel_ids`) _cannot_ be imported due channels being a separate resource. However, to add channels to an imported alert policy, you can import the policy, add the `channel_ids` attribute with the associated channel IDs, then run `pulumi up`. This will result in the original alert policy being destroyed and a new alert policy being created along with the channels being added to the policy.
+        Please note that channel IDs (`channel_ids`) _cannot_ be imported due channels being a separate resource. However, to add channels to an imported alert policy, you can import the policy, add the `channel_ids` attribute with the associated channel IDs, then run `pulumi up`. This will result in the original alert policy being destroyed and a new alert policy being created along with the channels being added to the policy.
 
         :param str resource_name: The name of the resource.
         :param pulumi.ResourceOptions opts: Options for the resource.
@@ -261,16 +283,34 @@ class AlertPolicy(pulumi.CustomResource):
         Use this resource to create and manage New Relic alert policies.
 
         ## Example Usage
+
         ### Basic Usage
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
 
         foo = newrelic.AlertPolicy("foo", incident_preference="PER_POLICY")
         ```
+        <!--End PulumiCodeChooser -->
+
         ### Provision multiple notification channels and add those channels to a policy
 
+        The following arguments are supported:
+
+          * `name` - (Required) The name of the policy.
+          * `incident_preference` - (Optional) The rollup strategy for the policy, which can have one of the following values (the default value is `PER_POLICY`):
+            * `PER_POLICY` - This sets the incident grouping preference of the policy to **One issue per policy**. Refer to [this page](https://docs.newrelic.com/docs/alerts-applied-intelligence/new-relic-alerts/alert-policies/specify-when-alerts-create-incidents/#preference-policy) for more details on this incident grouping preference.
+            * `PER_CONDITION` - This sets the incident grouping preference of the policy to **One issue per condition**. Refer to [this page](https://docs.newrelic.com/docs/alerts-applied-intelligence/new-relic-alerts/alert-policies/specify-when-alerts-create-incidents/#preference-condition) for more details on this incident grouping preference.
+            * `PER_CONDITION_AND_TARGET` - This sets the incident grouping preference of the policy to **One issue per condition and signal**. Refer to [this page](https://docs.newrelic.com/docs/alerts-applied-intelligence/new-relic-alerts/alert-policies/specify-when-alerts-create-incidents/#preference-signal) for more details on this incident grouping preference.
+          * `channel_ids` - (Optional) **DEPRECATED** The `channel_ids` argument is deprecated and will be removed in the next major release of the provider. An array of channel IDs (integers) to assign to the policy. Adding or removing channel IDs from this array will result in a new alert policy resource being created and the old one being destroyed. Also note that channel IDs _cannot_ be imported via `pulumi import` (see Import for info).
+          * `account_id` - (Optional) The New Relic account ID to operate on.  This allows the user to override the `account_id` attribute set on the provider. Defaults to the environment variable `NEW_RELIC_ACCOUNT_ID`.
+
+        ## Additional Examples
+
+        ##### Provision multiple notification channels and add those channels to a policy
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -297,7 +337,10 @@ class AlertPolicy(pulumi.CustomResource):
                 email_channel.id,
             ])
         ```
+        <!--End PulumiCodeChooser -->
+
         ### Reference existing notification channels and add those channel to a policy
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -312,6 +355,7 @@ class AlertPolicy(pulumi.CustomResource):
                 email_channel.id,
             ])
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Import
 
@@ -320,9 +364,9 @@ class AlertPolicy(pulumi.CustomResource):
         Example import:
 
         ```sh
-         $ pulumi import newrelic:index/alertPolicy:AlertPolicy foo 23423556:4593020
+        $ pulumi import newrelic:index/alertPolicy:AlertPolicy foo 23423556:4593020
         ```
-         Please note that channel IDs (`channel_ids`) _cannot_ be imported due channels being a separate resource. However, to add channels to an imported alert policy, you can import the policy, add the `channel_ids` attribute with the associated channel IDs, then run `pulumi up`. This will result in the original alert policy being destroyed and a new alert policy being created along with the channels being added to the policy.
+        Please note that channel IDs (`channel_ids`) _cannot_ be imported due channels being a separate resource. However, to add channels to an imported alert policy, you can import the policy, add the `channel_ids` attribute with the associated channel IDs, then run `pulumi up`. This will result in the original alert policy being destroyed and a new alert policy being created along with the channels being added to the policy.
 
         :param str resource_name: The name of the resource.
         :param AlertPolicyArgs args: The arguments to use to populate this resource's properties.

pulumi_newrelic/alert_policy_channel.py

@@ -139,6 +139,7 @@ class AlertPolicyChannel(pulumi.CustomResource):
 
         The example below will apply multiple alert channels to an existing New Relic alert policy.
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -167,15 +168,16 @@ class AlertPolicyChannel(pulumi.CustomResource):
                 slack_channel.id,
             ])
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Import
 
         Alert policy channels can be imported using the following notation: `<policyID>:<channelID>:<channelID>`, e.g.
 
         ```sh
-         $ pulumi import newrelic:index/alertPolicyChannel:AlertPolicyChannel foo 123456:3462754:2938324
+        $ pulumi import newrelic:index/alertPolicyChannel:AlertPolicyChannel foo 123456:3462754:2938324
         ```
-         When importing `newrelic_alert_policy_channel` resource, the attribute `channel_ids`* will be set in your Terraform state. You can import multiple channels as long as those channel IDs are included as part of the import ID hash.
+        When importing `newrelic_alert_policy_channel` resource, the attribute `channel_ids`* will be set in your Terraform state. You can import multiple channels as long as those channel IDs are included as part of the import ID hash.
 
         :param str resource_name: The name of the resource.
         :param pulumi.ResourceOptions opts: Options for the resource.
@@ -198,6 +200,7 @@ class AlertPolicyChannel(pulumi.CustomResource):
 
         The example below will apply multiple alert channels to an existing New Relic alert policy.
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -226,15 +229,16 @@ class AlertPolicyChannel(pulumi.CustomResource):
                 slack_channel.id,
             ])
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Import
 
         Alert policy channels can be imported using the following notation: `<policyID>:<channelID>:<channelID>`, e.g.
 
         ```sh
-         $ pulumi import newrelic:index/alertPolicyChannel:AlertPolicyChannel foo 123456:3462754:2938324
+        $ pulumi import newrelic:index/alertPolicyChannel:AlertPolicyChannel foo 123456:3462754:2938324
         ```
-         When importing `newrelic_alert_policy_channel` resource, the attribute `channel_ids`* will be set in your Terraform state. You can import multiple channels as long as those channel IDs are included as part of the import ID hash.
+        When importing `newrelic_alert_policy_channel` resource, the attribute `channel_ids`* will be set in your Terraform state. You can import multiple channels as long as those channel IDs are included as part of the import ID hash.
 
         :param str resource_name: The name of the resource.
         :param AlertPolicyChannelArgs args: The arguments to use to populate this resource's properties.

pulumi_newrelic/api_access_key.py

@@ -262,27 +262,17 @@ class ApiAccessKey(pulumi.CustomResource):
 
         ## Example Usage
 
-        ```python
-        import pulumi
-        import pulumi_newrelic as newrelic
-
-        foobar = newrelic.ApiAccessKey("foobar",
-            account_id=1234567,
-            ingest_type="LICENSE",
-            key_type="INGEST",
-            notes="To be used with service X")
-        ```
-
         > **WARNING:** Creating 'Ingest - License' and 'Ingest - Browser' keys using this resource is restricted to 'core' or 'full platform' New Relic user accounts. If you've signed up as a 'basic' user with New Relic, or have been added as a 'basic' user to your organization on New Relic, you would not be able to use your account to create 'Ingest' keys. If you see the message `"You do not have permission to create this key"` in the response of the API called by this resource, it could be owing to the aforementioned. For more insights into user account types on New Relic and associated privileges, please check out this [page](https://docs.newrelic.com/docs/accounts/accounts-billing/new-relic-one-user-management/user-type/#api-access).
 
         ## Import
 
-        Existing API access keys can be imported using a composite ID of `<api_access_key_id>:<key_type>`. `<key_type>` will be either `INGEST` or `USER`.
+        Existing API access keys can be imported using a composite ID of `<api_access_key_id>:<key_type>`. `<key_type>`
+        will be either `INGEST` or `USER`.
 
         For example:
 
         ```sh
-         $ pulumi import newrelic:index/apiAccessKey:ApiAccessKey foobar "1234567:INGEST"
+        $ pulumi import newrelic:index/apiAccessKey:ApiAccessKey foobar "1234567:INGEST"
         ```
 
         :param str resource_name: The name of the resource.
@@ -317,27 +307,17 @@ class ApiAccessKey(pulumi.CustomResource):
 
         ## Example Usage
 
-        ```python
-        import pulumi
-        import pulumi_newrelic as newrelic
-
-        foobar = newrelic.ApiAccessKey("foobar",
-            account_id=1234567,
-            ingest_type="LICENSE",
-            key_type="INGEST",
-            notes="To be used with service X")
-        ```
-
         > **WARNING:** Creating 'Ingest - License' and 'Ingest - Browser' keys using this resource is restricted to 'core' or 'full platform' New Relic user accounts. If you've signed up as a 'basic' user with New Relic, or have been added as a 'basic' user to your organization on New Relic, you would not be able to use your account to create 'Ingest' keys. If you see the message `"You do not have permission to create this key"` in the response of the API called by this resource, it could be owing to the aforementioned. For more insights into user account types on New Relic and associated privileges, please check out this [page](https://docs.newrelic.com/docs/accounts/accounts-billing/new-relic-one-user-management/user-type/#api-access).
 
         ## Import
 
-        Existing API access keys can be imported using a composite ID of `<api_access_key_id>:<key_type>`. `<key_type>` will be either `INGEST` or `USER`.
+        Existing API access keys can be imported using a composite ID of `<api_access_key_id>:<key_type>`. `<key_type>`
+        will be either `INGEST` or `USER`.
 
         For example:
 
         ```sh
-         $ pulumi import newrelic:index/apiAccessKey:ApiAccessKey foobar "1234567:INGEST"
+        $ pulumi import newrelic:index/apiAccessKey:ApiAccessKey foobar "1234567:INGEST"
         ```
 
         :param str resource_name: The name of the resource.

pulumi_newrelic/browser_application.py

@@ -236,6 +236,7 @@ class BrowserApplication(pulumi.CustomResource):
         ## Example Usage
 
         Basic usage to create a standalone browser application.
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -245,12 +246,13 @@ class BrowserApplication(pulumi.CustomResource):
             distributed_tracing_enabled=True,
             loader_type="SPA")
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Import
 
         Browser applications can be imported using the GUID of the browser application.
 
-         bash
+        bash
 
         ```sh
         $ pulumi import newrelic:index/browserApplication:BrowserApplication foo <GUID>
@@ -276,6 +278,7 @@ class BrowserApplication(pulumi.CustomResource):
         ## Example Usage
 
         Basic usage to create a standalone browser application.
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -285,12 +288,13 @@ class BrowserApplication(pulumi.CustomResource):
             distributed_tracing_enabled=True,
             loader_type="SPA")
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Import
 
         Browser applications can be imported using the GUID of the browser application.
 
-         bash
+        bash
 
         ```sh
         $ pulumi import newrelic:index/browserApplication:BrowserApplication foo <GUID>

pulumi_newrelic/cloud/aws_govcloud_integrations.py

@@ -777,7 +777,7 @@ class AwsGovcloudIntegrations(pulumi.CustomResource):
 
         Integrate AWSGovCloud accounts can be imported using the `id`, e.g.
 
-         bash
+        bash
 
         ```sh
         $ pulumi import newrelic:cloud/awsGovcloudIntegrations:AwsGovcloudIntegrations foo <id>
@@ -831,7 +831,7 @@ class AwsGovcloudIntegrations(pulumi.CustomResource):
 
         Integrate AWSGovCloud accounts can be imported using the `id`, e.g.
 
-         bash
+        bash
 
         ```sh
         $ pulumi import newrelic:cloud/awsGovcloudIntegrations:AwsGovcloudIntegrations foo <id>

pulumi_newrelic/cloud/aws_govcloud_link_account.py

@@ -243,6 +243,7 @@ class AwsGovcloudLinkAccount(pulumi.CustomResource):
 
         ## Example Usage
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -254,12 +255,13 @@ class AwsGovcloudLinkAccount(pulumi.CustomResource):
             metric_collection_mode="PULL",
             secret_access_key="secret access key of the aws govcloud account")
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Import
 
         Linked AWSGovCloud accounts can be imported using the `id`, e.g.
 
-         bash
+        bash
 
         ```sh
         $ pulumi import newrelic:cloud/awsGovcloudLinkAccount:AwsGovcloudLinkAccount foo <id>
@@ -295,6 +297,7 @@ class AwsGovcloudLinkAccount(pulumi.CustomResource):
 
         ## Example Usage
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -306,12 +309,13 @@ class AwsGovcloudLinkAccount(pulumi.CustomResource):
             metric_collection_mode="PULL",
             secret_access_key="secret access key of the aws govcloud account")
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Import
 
         Linked AWSGovCloud accounts can be imported using the `id`, e.g.
 
-         bash
+        bash
 
         ```sh
         $ pulumi import newrelic:cloud/awsGovcloudLinkAccount:AwsGovcloudLinkAccount foo <id>

pulumi_newrelic/cloud/aws_integrations.py

@@ -2075,6 +2075,7 @@ class AwsIntegrations(pulumi.CustomResource):
 
         Leave an integration block empty to use its default configuration. You can also use the full example, including the AWS set up, found in our guides.
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -2361,12 +2362,13 @@ class AwsIntegrations(pulumi.CustomResource):
                 metrics_polling_interval=6000,
             ))
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Import
 
         Linked AWS account integrations can be imported using the `id`, e.g.
 
-         bash
+        bash
 
         ```sh
         $ pulumi import newrelic:cloud/awsIntegrations:AwsIntegrations foo <id>
@@ -2511,6 +2513,7 @@ class AwsIntegrations(pulumi.CustomResource):
 
         Leave an integration block empty to use its default configuration. You can also use the full example, including the AWS set up, found in our guides.
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -2797,12 +2800,13 @@ class AwsIntegrations(pulumi.CustomResource):
                 metrics_polling_interval=6000,
             ))
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Import
 
         Linked AWS account integrations can be imported using the `id`, e.g.
 
-         bash
+        bash
 
         ```sh
         $ pulumi import newrelic:cloud/awsIntegrations:AwsIntegrations foo <id>

pulumi_newrelic/cloud/aws_link_account.py

@@ -179,6 +179,7 @@ class AwsLinkAccount(pulumi.CustomResource):
 
         You can also use the full example, including the AWS set up, found in our guides.
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -187,12 +188,13 @@ class AwsLinkAccount(pulumi.CustomResource):
             arn="arn:aws:service:region:account-id:resource-id",
             metric_collection_mode="PUSH")
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Import
 
         Linked AWS accounts can be imported using the `id`, e.g.
 
-         bash
+        bash
 
         ```sh
         $ pulumi import newrelic:cloud/awsLinkAccount:AwsLinkAccount foo <id>
@@ -226,6 +228,7 @@ class AwsLinkAccount(pulumi.CustomResource):
 
         You can also use the full example, including the AWS set up, found in our guides.
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -234,12 +237,13 @@ class AwsLinkAccount(pulumi.CustomResource):
             arn="arn:aws:service:region:account-id:resource-id",
             metric_collection_mode="PUSH")
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Import
 
         Linked AWS accounts can be imported using the `id`, e.g.
 
-         bash
+        bash
 
         ```sh
         $ pulumi import newrelic:cloud/awsLinkAccount:AwsLinkAccount foo <id>