pulumi-newrelic 5.20.0a1709643785__py3-none-any.whl → 5.21.0a1710157101__py3-none-any.whl

pulumi_newrelic/insights/event.py

@@ -72,6 +72,7 @@ class Event(pulumi.CustomResource):
 
         ## Example Usage
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -97,6 +98,8 @@ class Event(pulumi.CustomResource):
             type="MyEvent",
         )])
         ```
+        <!--End PulumiCodeChooser -->
+
         ## Events
 
         The `event` mapping supports the following arguments:
@@ -128,6 +131,7 @@ class Event(pulumi.CustomResource):
 
         ## Example Usage
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -153,6 +157,8 @@ class Event(pulumi.CustomResource):
             type="MyEvent",
         )])
         ```
+        <!--End PulumiCodeChooser -->
+
         ## Events
 
         The `event` mapping supports the following arguments:

pulumi_newrelic/log_parsing_rule.py

@@ -315,6 +315,7 @@ class LogParsingRule(pulumi.CustomResource):
         ## Example Usage
 
         Use this example to create the log parse rule.
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -326,10 +327,13 @@ class LogParsingRule(pulumi.CustomResource):
             lucene="logtype:linux_messages",
             nrql="SELECT * FROM Log WHERE logtype = 'linux_messages'")
         ```
+        <!--End PulumiCodeChooser -->
+
         ## Additional Example
 
         Use this example to validate a grok pattern and create the log parse rule.  More
         information on grok pattern can be found [here](https://docs.newrelic.com/docs/logs/ui-data/parsing/#grok)
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -344,12 +348,13 @@ class LogParsingRule(pulumi.CustomResource):
             nrql="SELECT * FROM Log WHERE logtype = 'linux_messages'",
             matched=grok.test_groks[0].matched)
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Import
 
         New Relic log parsing rule can be imported using the rule ID, e.g.
 
-         bash
+        bash
 
         ```sh
         $ pulumi import newrelic:index/logParsingRule:LogParsingRule foo 3456789
@@ -378,6 +383,7 @@ class LogParsingRule(pulumi.CustomResource):
         ## Example Usage
 
         Use this example to create the log parse rule.
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -389,10 +395,13 @@ class LogParsingRule(pulumi.CustomResource):
             lucene="logtype:linux_messages",
             nrql="SELECT * FROM Log WHERE logtype = 'linux_messages'")
         ```
+        <!--End PulumiCodeChooser -->
+
         ## Additional Example
 
         Use this example to validate a grok pattern and create the log parse rule.  More
         information on grok pattern can be found [here](https://docs.newrelic.com/docs/logs/ui-data/parsing/#grok)
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -407,12 +416,13 @@ class LogParsingRule(pulumi.CustomResource):
             nrql="SELECT * FROM Log WHERE logtype = 'linux_messages'",
             matched=grok.test_groks[0].matched)
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Import
 
         New Relic log parsing rule can be imported using the rule ID, e.g.
 
-         bash
+        bash
 
         ```sh
         $ pulumi import newrelic:index/logParsingRule:LogParsingRule foo 3456789

pulumi_newrelic/monitor_downtime.py

@@ -374,6 +374,7 @@ class MonitorDowntime(pulumi.CustomResource):
 
         ## Example Usage
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -395,13 +396,16 @@ class MonitorDowntime(pulumi.CustomResource):
             start_time="2023-11-30T10:30:00",
             time_zone="Asia/Kolkata")
         ```
+        <!--End PulumiCodeChooser -->
         Monitor Downtimes are of four types; **one-time**, **daily**, **weekly** and **monthly**. For more details on each type and the right arguments that go with them, check out the argument reference and examples sections below.
+
         ## Examples
 
         ### One-Time Monitor Downtime
 
         The below example illustrates creating a **one-time** monitor downtime.
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -416,6 +420,7 @@ class MonitorDowntime(pulumi.CustomResource):
             start_time="2023-12-04T10:15:00",
             time_zone="America/Los_Angeles")
         ```
+        <!--End PulumiCodeChooser -->
 
         ### Daily Monitor Downtime
 
@@ -423,6 +428,7 @@ class MonitorDowntime(pulumi.CustomResource):
 
         Note that `end_repeat` has been specified in the configuration; however, this is optional, in accordance with the rules of `end_repeat` specified in the argument reference section above. This example uses the `on_date` nested argument of `end_repeat`, however, the other nested argument, `on_repeat` may also be used _instead_, as you may see in some of the other examples below; though both `on_date` and `on_repeat` cannot be specified together, as they are mutually exclusive.
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -440,6 +446,7 @@ class MonitorDowntime(pulumi.CustomResource):
             start_time="2023-12-04T18:15:00",
             time_zone="Asia/Kolkata")
         ```
+        <!--End PulumiCodeChooser -->
 
         ### Weekly Monitor Downtime
 
@@ -447,6 +454,7 @@ class MonitorDowntime(pulumi.CustomResource):
 
         Note that `maintenance_days` has been specified in the configuration as it is required with weekly monitor downtimes; and `end_repeat` has not been specified as it is optional, all in accordance with the rules of these arguments specified in the argument reference section above.
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -465,6 +473,7 @@ class MonitorDowntime(pulumi.CustomResource):
             start_time="2023-12-04T14:15:00",
             time_zone="US/Hawaii")
         ```
+        <!--End PulumiCodeChooser -->
 
         ### Monthly Monitor Downtime
 
@@ -472,6 +481,7 @@ class MonitorDowntime(pulumi.CustomResource):
 
         Note that `frequency` has been specified in the configuration as it is required with monthly monitor downtimes, and `end_repeat` has been specified too, though it is optional. `frequency` has been specified with `days_of_week` comprising both of its nested arguments, `ordinal_day_of_month` and `week_day`; all in accordance with the rules of these arguments specified in the argument reference section above.
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -495,7 +505,9 @@ class MonitorDowntime(pulumi.CustomResource):
             start_time="2023-12-04T07:15:00",
             time_zone="Europe/Dublin")
         ```
+        <!--End PulumiCodeChooser -->
         However, the `frequency` block in monthly monitor downtimes may also be specified with its other nested argument, `days_of_month`, as shown in the example below - though both `days_of_month` and `days_of_week` cannot be specified together, as they are mutually exclusive.
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -521,12 +533,13 @@ class MonitorDowntime(pulumi.CustomResource):
             start_time="2023-12-04T07:15:00",
             time_zone="Europe/Dublin")
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Import
 
         A monitor downtime can be imported into Terraform configuration using its `guid`, i.e.
 
-         bash
+        bash
 
         ```sh
         $ pulumi import newrelic:index/monitorDowntime:MonitorDowntime monitor <guid>
@@ -558,6 +571,7 @@ class MonitorDowntime(pulumi.CustomResource):
 
         ## Example Usage
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -579,13 +593,16 @@ class MonitorDowntime(pulumi.CustomResource):
             start_time="2023-11-30T10:30:00",
             time_zone="Asia/Kolkata")
         ```
+        <!--End PulumiCodeChooser -->
         Monitor Downtimes are of four types; **one-time**, **daily**, **weekly** and **monthly**. For more details on each type and the right arguments that go with them, check out the argument reference and examples sections below.
+
         ## Examples
 
         ### One-Time Monitor Downtime
 
         The below example illustrates creating a **one-time** monitor downtime.
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -600,6 +617,7 @@ class MonitorDowntime(pulumi.CustomResource):
             start_time="2023-12-04T10:15:00",
             time_zone="America/Los_Angeles")
         ```
+        <!--End PulumiCodeChooser -->
 
         ### Daily Monitor Downtime
 
@@ -607,6 +625,7 @@ class MonitorDowntime(pulumi.CustomResource):
 
         Note that `end_repeat` has been specified in the configuration; however, this is optional, in accordance with the rules of `end_repeat` specified in the argument reference section above. This example uses the `on_date` nested argument of `end_repeat`, however, the other nested argument, `on_repeat` may also be used _instead_, as you may see in some of the other examples below; though both `on_date` and `on_repeat` cannot be specified together, as they are mutually exclusive.
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -624,6 +643,7 @@ class MonitorDowntime(pulumi.CustomResource):
             start_time="2023-12-04T18:15:00",
             time_zone="Asia/Kolkata")
         ```
+        <!--End PulumiCodeChooser -->
 
         ### Weekly Monitor Downtime
 
@@ -631,6 +651,7 @@ class MonitorDowntime(pulumi.CustomResource):
 
         Note that `maintenance_days` has been specified in the configuration as it is required with weekly monitor downtimes; and `end_repeat` has not been specified as it is optional, all in accordance with the rules of these arguments specified in the argument reference section above.
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -649,6 +670,7 @@ class MonitorDowntime(pulumi.CustomResource):
             start_time="2023-12-04T14:15:00",
             time_zone="US/Hawaii")
         ```
+        <!--End PulumiCodeChooser -->
 
         ### Monthly Monitor Downtime
 
@@ -656,6 +678,7 @@ class MonitorDowntime(pulumi.CustomResource):
 
         Note that `frequency` has been specified in the configuration as it is required with monthly monitor downtimes, and `end_repeat` has been specified too, though it is optional. `frequency` has been specified with `days_of_week` comprising both of its nested arguments, `ordinal_day_of_month` and `week_day`; all in accordance with the rules of these arguments specified in the argument reference section above.
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -679,7 +702,9 @@ class MonitorDowntime(pulumi.CustomResource):
             start_time="2023-12-04T07:15:00",
             time_zone="Europe/Dublin")
         ```
+        <!--End PulumiCodeChooser -->
         However, the `frequency` block in monthly monitor downtimes may also be specified with its other nested argument, `days_of_month`, as shown in the example below - though both `days_of_month` and `days_of_week` cannot be specified together, as they are mutually exclusive.
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -705,12 +730,13 @@ class MonitorDowntime(pulumi.CustomResource):
             start_time="2023-12-04T07:15:00",
             time_zone="Europe/Dublin")
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Import
 
         A monitor downtime can be imported into Terraform configuration using its `guid`, i.e.
 
-         bash
+        bash
 
         ```sh
         $ pulumi import newrelic:index/monitorDowntime:MonitorDowntime monitor <guid>

pulumi_newrelic/notification_channel.py

@@ -286,6 +286,7 @@ class NotificationChannel(pulumi.CustomResource):
         ## Example Usage
 
         ##### [Webhook](https://docs.newrelic.com/docs/apis/nerdgraph/examples/nerdgraph-api-notifications-channels/#webhook)
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -301,7 +302,9 @@ class NotificationChannel(pulumi.CustomResource):
             )],
             type="WEBHOOK")
         ```
+        <!--End PulumiCodeChooser -->
         See additional examples.
+
         ## Additional Examples
 
         > **NOTE:** We support all properties. The mentioned properties are just an example.
@@ -309,6 +312,7 @@ class NotificationChannel(pulumi.CustomResource):
         ##### [ServiceNow](https://docs.newrelic.com/docs/apis/nerdgraph/examples/nerdgraph-api-notifications-channels/#servicenow)
         To see the properties’ keys for your account, check ServiceNow incidents table.
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -329,8 +333,10 @@ class NotificationChannel(pulumi.CustomResource):
             ],
             type="SERVICENOW_INCIDENTS")
         ```
+        <!--End PulumiCodeChooser -->
 
         ##### [Email](https://docs.newrelic.com/docs/apis/nerdgraph/examples/nerdgraph-api-notifications-channels/#email)
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -351,8 +357,10 @@ class NotificationChannel(pulumi.CustomResource):
             ],
             type="EMAIL")
         ```
+        <!--End PulumiCodeChooser -->
 
         ##### [Jira Classic](https://docs.newrelic.com/docs/apis/nerdgraph/examples/nerdgraph-api-notifications-channels/#jira)
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -381,8 +389,10 @@ class NotificationChannel(pulumi.CustomResource):
             ],
             type="JIRA_CLASSIC")
         ```
+        <!--End PulumiCodeChooser -->
 
         ##### [PagerDuty with account integration](https://docs.newrelic.com/docs/apis/nerdgraph/examples/nerdgraph-api-notifications-channels/#pagerduty)
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -426,8 +436,10 @@ class NotificationChannel(pulumi.CustomResource):
             ],
             type="PAGERDUTY_ACCOUNT_INTEGRATION")
         ```
+        <!--End PulumiCodeChooser -->
 
         ##### [PagerDuty with service integration](https://docs.newrelic.com/docs/apis/nerdgraph/examples/nerdgraph-api-notifications-channels/#pagerduty)
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -462,8 +474,10 @@ class NotificationChannel(pulumi.CustomResource):
             ],
             type="PAGERDUTY_SERVICE_INTEGRATION")
         ```
+        <!--End PulumiCodeChooser -->
 
         #### Mobile Push
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -474,8 +488,10 @@ class NotificationChannel(pulumi.CustomResource):
             product="IINT",
             type="MOBILE_PUSH")
         ```
+        <!--End PulumiCodeChooser -->
 
         #### [AWS Event Bridge](https://docs.newrelic.com/docs/apis/nerdgraph/examples/nerdgraph-api-notifications-channels/#eventBridge)
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -496,8 +512,10 @@ class NotificationChannel(pulumi.CustomResource):
             ],
             type="EVENT_BRIDGE")
         ```
+        <!--End PulumiCodeChooser -->
 
         #### [SLACK](https://docs.newrelic.com/docs/apis/nerdgraph/examples/nerdgraph-api-notifications-channels/#slack)
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -518,6 +536,7 @@ class NotificationChannel(pulumi.CustomResource):
             ],
             type="SLACK")
         ```
+        <!--End PulumiCodeChooser -->
 
         > **NOTE:** Sensitive data such as channel API keys, service keys, etc are not returned from the underlying API for security reasons and may not be set in state when importing.
 
@@ -526,6 +545,7 @@ class NotificationChannel(pulumi.CustomResource):
         Create a destination resource and reference that destination to the channel resource:
 
         ### Create a destination
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -542,8 +562,10 @@ class NotificationChannel(pulumi.CustomResource):
             )],
             type="WEBHOOK")
         ```
+        <!--End PulumiCodeChooser -->
 
         ### Create a channel
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -559,6 +581,7 @@ class NotificationChannel(pulumi.CustomResource):
                 label="Payload Template",
             )])
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Additional Information
 
@@ -570,9 +593,9 @@ class NotificationChannel(pulumi.CustomResource):
 
         Channels can only be used by a single workflow, therefore importing them is not particularly useful, because in the UI channels are created upon workflow creation.
 
-         Additionally, the channel id isn't available via the UI, and you'd need to look it up with the `channels` query in the NerdGraph API.
+        Additionally, the channel id isn't available via the UI, and you'd need to look it up with the `channels` query in the NerdGraph API.
 
-         That being said, importing is possible using -
+        That being said, importing is possible using -
 
         ```sh
         $ pulumi import newrelic:index/notificationChannel:NotificationChannel foo <destination_id>
@@ -602,6 +625,7 @@ class NotificationChannel(pulumi.CustomResource):
         ## Example Usage
 
         ##### [Webhook](https://docs.newrelic.com/docs/apis/nerdgraph/examples/nerdgraph-api-notifications-channels/#webhook)
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -617,7 +641,9 @@ class NotificationChannel(pulumi.CustomResource):
             )],
             type="WEBHOOK")
         ```
+        <!--End PulumiCodeChooser -->
         See additional examples.
+
         ## Additional Examples
 
         > **NOTE:** We support all properties. The mentioned properties are just an example.
@@ -625,6 +651,7 @@ class NotificationChannel(pulumi.CustomResource):
         ##### [ServiceNow](https://docs.newrelic.com/docs/apis/nerdgraph/examples/nerdgraph-api-notifications-channels/#servicenow)
         To see the properties’ keys for your account, check ServiceNow incidents table.
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -645,8 +672,10 @@ class NotificationChannel(pulumi.CustomResource):
             ],
             type="SERVICENOW_INCIDENTS")
         ```
+        <!--End PulumiCodeChooser -->
 
         ##### [Email](https://docs.newrelic.com/docs/apis/nerdgraph/examples/nerdgraph-api-notifications-channels/#email)
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -667,8 +696,10 @@ class NotificationChannel(pulumi.CustomResource):
             ],
             type="EMAIL")
         ```
+        <!--End PulumiCodeChooser -->
 
         ##### [Jira Classic](https://docs.newrelic.com/docs/apis/nerdgraph/examples/nerdgraph-api-notifications-channels/#jira)
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -697,8 +728,10 @@ class NotificationChannel(pulumi.CustomResource):
             ],
             type="JIRA_CLASSIC")
         ```
+        <!--End PulumiCodeChooser -->
 
         ##### [PagerDuty with account integration](https://docs.newrelic.com/docs/apis/nerdgraph/examples/nerdgraph-api-notifications-channels/#pagerduty)
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -742,8 +775,10 @@ class NotificationChannel(pulumi.CustomResource):
             ],
             type="PAGERDUTY_ACCOUNT_INTEGRATION")
         ```
+        <!--End PulumiCodeChooser -->
 
         ##### [PagerDuty with service integration](https://docs.newrelic.com/docs/apis/nerdgraph/examples/nerdgraph-api-notifications-channels/#pagerduty)
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -778,8 +813,10 @@ class NotificationChannel(pulumi.CustomResource):
             ],
             type="PAGERDUTY_SERVICE_INTEGRATION")
         ```
+        <!--End PulumiCodeChooser -->
 
         #### Mobile Push
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -790,8 +827,10 @@ class NotificationChannel(pulumi.CustomResource):
             product="IINT",
             type="MOBILE_PUSH")
         ```
+        <!--End PulumiCodeChooser -->
 
         #### [AWS Event Bridge](https://docs.newrelic.com/docs/apis/nerdgraph/examples/nerdgraph-api-notifications-channels/#eventBridge)
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -812,8 +851,10 @@ class NotificationChannel(pulumi.CustomResource):
             ],
             type="EVENT_BRIDGE")
         ```
+        <!--End PulumiCodeChooser -->
 
         #### [SLACK](https://docs.newrelic.com/docs/apis/nerdgraph/examples/nerdgraph-api-notifications-channels/#slack)
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -834,6 +875,7 @@ class NotificationChannel(pulumi.CustomResource):
             ],
             type="SLACK")
         ```
+        <!--End PulumiCodeChooser -->
 
         > **NOTE:** Sensitive data such as channel API keys, service keys, etc are not returned from the underlying API for security reasons and may not be set in state when importing.
 
@@ -842,6 +884,7 @@ class NotificationChannel(pulumi.CustomResource):
         Create a destination resource and reference that destination to the channel resource:
 
         ### Create a destination
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -858,8 +901,10 @@ class NotificationChannel(pulumi.CustomResource):
             )],
             type="WEBHOOK")
         ```
+        <!--End PulumiCodeChooser -->
 
         ### Create a channel
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -875,6 +920,7 @@ class NotificationChannel(pulumi.CustomResource):
                 label="Payload Template",
             )])
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Additional Information
 
@@ -886,9 +932,9 @@ class NotificationChannel(pulumi.CustomResource):
 
         Channels can only be used by a single workflow, therefore importing them is not particularly useful, because in the UI channels are created upon workflow creation.
 
-         Additionally, the channel id isn't available via the UI, and you'd need to look it up with the `channels` query in the NerdGraph API.
+        Additionally, the channel id isn't available via the UI, and you'd need to look it up with the `channels` query in the NerdGraph API.
 
-         That being said, importing is possible using -
+        That being said, importing is possible using -
 
         ```sh
         $ pulumi import newrelic:index/notificationChannel:NotificationChannel foo <destination_id>