pulumi-newrelic 5.23.0a1713561620__py3-none-any.whl → 5.23.0a1713984329__py3-none-any.whl

pulumi_newrelic/get_service_level_alert_helper.py

@@ -170,7 +170,6 @@ def get_service_level_alert_helper(alert_type: Optional[str] = None,
 
     Firstly set up your service level objective, we recommend using local variables for the `target` and `time_window.rolling.count`, as they are also necessary for the helper.
 
-    <!--Start PulumiCodeChooser -->
     ```python
     import pulumi
     import pulumi_newrelic as newrelic
@@ -202,14 +201,12 @@ def get_service_level_alert_helper(alert_type: Optional[str] = None,
             ),
         ))
     ```
-    <!--End PulumiCodeChooser -->
     Then use the helper to obtain the necessary fields to set up an alert on that Service Level.
     Note that the Service Level was set up using bad events, that's why `is_bad_events` is set to `true`.
     If the Service Level was configured with good events that would be unnecessary as the field defaults to `false`.
 
     Here is an example of a `slow_burn` alert.
 
-    <!--Start PulumiCodeChooser -->
     ```python
     import pulumi
     import pulumi_newrelic as newrelic
@@ -241,11 +238,9 @@ def get_service_level_alert_helper(alert_type: Optional[str] = None,
         aggregation_delay="120",
         slide_by=900)
     ```
-    <!--End PulumiCodeChooser -->
 
     Here is an example of a custom alert:
 
-    <!--Start PulumiCodeChooser -->
     ```python
     import pulumi
     import pulumi_newrelic as newrelic
@@ -279,16 +274,6 @@ def get_service_level_alert_helper(alert_type: Optional[str] = None,
         aggregation_delay="120",
         slide_by=60)
     ```
-    <!--End PulumiCodeChooser -->
-
-
-    :param str alert_type: The type of alert we want to set. Valid values are:
-    :param int custom_evaluation_period: Aggregation window taken into consideration in seconds. Mandatory if `alert_type` is `custom`.
-    :param float custom_tolerated_budget_consumption: How much budget you tolerate to consume during the custom evaluation period, valid values between `0` and `100`. Mandatory if `alert_type` is `custom`.
-    :param bool is_bad_events: If the SLI is defined using bad events. Defaults to `false`
-    :param str sli_guid: The guid of the sli we want to set the alert on.
-    :param int slo_period: The time window of the Service Level Objective in days. Valid values are `1`, `7` and `28`.
-    :param float slo_target: The target of the Service Level Objective, valid values between `0` and `100`.
     """
     __args__ = dict()
     __args__['alertType'] = alert_type
@@ -332,7 +317,6 @@ def get_service_level_alert_helper_output(alert_type: Optional[pulumi.Input[str]
 
     Firstly set up your service level objective, we recommend using local variables for the `target` and `time_window.rolling.count`, as they are also necessary for the helper.
 
-    <!--Start PulumiCodeChooser -->
     ```python
     import pulumi
     import pulumi_newrelic as newrelic
@@ -364,14 +348,12 @@ def get_service_level_alert_helper_output(alert_type: Optional[pulumi.Input[str]
             ),
         ))
     ```
-    <!--End PulumiCodeChooser -->
     Then use the helper to obtain the necessary fields to set up an alert on that Service Level.
     Note that the Service Level was set up using bad events, that's why `is_bad_events` is set to `true`.
     If the Service Level was configured with good events that would be unnecessary as the field defaults to `false`.
 
     Here is an example of a `slow_burn` alert.
 
-    <!--Start PulumiCodeChooser -->
     ```python
     import pulumi
     import pulumi_newrelic as newrelic
@@ -403,11 +385,9 @@ def get_service_level_alert_helper_output(alert_type: Optional[pulumi.Input[str]
         aggregation_delay="120",
         slide_by=900)
     ```
-    <!--End PulumiCodeChooser -->
 
     Here is an example of a custom alert:
 
-    <!--Start PulumiCodeChooser -->
     ```python
     import pulumi
     import pulumi_newrelic as newrelic
@@ -441,15 +421,5 @@ def get_service_level_alert_helper_output(alert_type: Optional[pulumi.Input[str]
         aggregation_delay="120",
         slide_by=60)
     ```
-    <!--End PulumiCodeChooser -->
-
-
-    :param str alert_type: The type of alert we want to set. Valid values are:
-    :param int custom_evaluation_period: Aggregation window taken into consideration in seconds. Mandatory if `alert_type` is `custom`.
-    :param float custom_tolerated_budget_consumption: How much budget you tolerate to consume during the custom evaluation period, valid values between `0` and `100`. Mandatory if `alert_type` is `custom`.
-    :param bool is_bad_events: If the SLI is defined using bad events. Defaults to `false`
-    :param str sli_guid: The guid of the sli we want to set the alert on.
-    :param int slo_period: The time window of the Service Level Objective in days. Valid values are `1`, `7` and `28`.
-    :param float slo_target: The target of the Service Level Objective, valid values between `0` and `100`.
     """
     ...

pulumi_newrelic/get_test_grok_pattern.py

@@ -91,7 +91,6 @@ def get_test_grok_pattern(account_id: Optional[int] = None,
     """
     ## Example Usage
 
-    <!--Start PulumiCodeChooser -->
     ```python
     import pulumi
     import pulumi_newrelic as newrelic
@@ -103,7 +102,6 @@ def get_test_grok_pattern(account_id: Optional[int] = None,
             "bytes_received: 2048",
         ])
     ```
-    <!--End PulumiCodeChooser -->
 
 
     :param int account_id: The New Relic account ID to operate on.  This allows you to override the `account_id` attribute set on the provider. Defaults to the environment variable `NEW_RELIC_ACCOUNT_ID`.
@@ -133,7 +131,6 @@ def get_test_grok_pattern_output(account_id: Optional[pulumi.Input[Optional[int]
     """
     ## Example Usage
 
-    <!--Start PulumiCodeChooser -->
     ```python
     import pulumi
     import pulumi_newrelic as newrelic
@@ -145,7 +142,6 @@ def get_test_grok_pattern_output(account_id: Optional[pulumi.Input[Optional[int]
             "bytes_received: 2048",
         ])
     ```
-    <!--End PulumiCodeChooser -->
 
 
     :param int account_id: The New Relic account ID to operate on.  This allows you to override the `account_id` attribute set on the provider. Defaults to the environment variable `NEW_RELIC_ACCOUNT_ID`.

pulumi_newrelic/get_user.py

@@ -81,7 +81,6 @@ def get_user(authentication_domain_id: Optional[str] = None,
     ## Example Usage
 
     The below example illustrates fetching a the ID of a user (and other arguments) using the ID of the authentication domain the user belongs to, as well as a name and/or email ID, which can be used as criteria to search for a user who matches these specified parameters.
-    <!--Start PulumiCodeChooser -->
     ```python
     import pulumi
     import pulumi_newrelic as newrelic
@@ -92,7 +91,6 @@ def get_user(authentication_domain_id: Optional[str] = None,
     user_two = newrelic.get_user(authentication_domain_id=foo.id,
         email_id="test_user@random.com")
     ```
-    <!--End PulumiCodeChooser -->
 
 
     :param str authentication_domain_id: The ID of the authentication domain the user to be searched for belongs to.
@@ -130,7 +128,6 @@ def get_user_output(authentication_domain_id: Optional[pulumi.Input[str]] = None
     ## Example Usage
 
     The below example illustrates fetching a the ID of a user (and other arguments) using the ID of the authentication domain the user belongs to, as well as a name and/or email ID, which can be used as criteria to search for a user who matches these specified parameters.
-    <!--Start PulumiCodeChooser -->
     ```python
     import pulumi
     import pulumi_newrelic as newrelic
@@ -141,7 +138,6 @@ def get_user_output(authentication_domain_id: Optional[pulumi.Input[str]] = None
     user_two = newrelic.get_user(authentication_domain_id=foo.id,
         email_id="test_user@random.com")
     ```
-    <!--End PulumiCodeChooser -->
 
 
     :param str authentication_domain_id: The ID of the authentication domain the user to be searched for belongs to.

pulumi_newrelic/group.py

@@ -152,7 +152,6 @@ class Group(pulumi.CustomResource):
 
         ## Example Usage
 
-        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -166,7 +165,6 @@ class Group(pulumi.CustomResource):
                 "2221110000",
             ])
         ```
-        <!--End PulumiCodeChooser -->
 
         ## Additional Examples
 
@@ -174,7 +172,6 @@ class Group(pulumi.CustomResource):
 
         The following example illustrates the creation of a group using the `Group` resource, to which users created using the `User` resource are added.
 
-        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -198,13 +195,11 @@ class Group(pulumi.CustomResource):
                 bar.id,
             ])
         ```
-        <!--End PulumiCodeChooser -->
 
         ### Addition of Existing Users to a New Group
 
         The following example demonstrates the usage of the `Group` resource to create a group, wherein the `User` data source is employed to associate existing users with the newly formed group.
 
-        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -222,7 +217,6 @@ class Group(pulumi.CustomResource):
                 bar.id,
             ])
         ```
-        <!--End PulumiCodeChooser -->
 
         > **NOTE** Please note that the addition of users to groups is only possible when both the group and the users to be added to it belong to the _same authentication domain_. If the group being created and the users being added to it belong to different authentication domains, an error indicating `user not found` or an equivalent error will be thrown.
 
@@ -255,7 +249,6 @@ class Group(pulumi.CustomResource):
 
         ## Example Usage
 
-        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -269,7 +262,6 @@ class Group(pulumi.CustomResource):
                 "2221110000",
             ])
         ```
-        <!--End PulumiCodeChooser -->
 
         ## Additional Examples
 
@@ -277,7 +269,6 @@ class Group(pulumi.CustomResource):
 
         The following example illustrates the creation of a group using the `Group` resource, to which users created using the `User` resource are added.
 
-        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -301,13 +292,11 @@ class Group(pulumi.CustomResource):
                 bar.id,
             ])
         ```
-        <!--End PulumiCodeChooser -->
 
         ### Addition of Existing Users to a New Group
 
         The following example demonstrates the usage of the `Group` resource to create a group, wherein the `User` data source is employed to associate existing users with the newly formed group.
 
-        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -325,7 +314,6 @@ class Group(pulumi.CustomResource):
                 bar.id,
             ])
         ```
-        <!--End PulumiCodeChooser -->
 
         > **NOTE** Please note that the addition of users to groups is only possible when both the group and the users to be added to it belong to the _same authentication domain_. If the group being created and the users being added to it belong to different authentication domains, an error indicating `user not found` or an equivalent error will be thrown.