pulumi-newrelic 5.31.0a1724997093__py3-none-any.whl → 5.31.1__py3-none-any.whl

pulumi_newrelic/infra_alert_condition.py

@@ -595,7 +595,7 @@ class InfraAlertCondition(pulumi.CustomResource):
         """
         Use this resource to create and manage Infrastructure alert conditions in New Relic.
 
-        > **WARNING:** The `InfraAlertCondition` resource is deprecated and will be removed in the next major release. The resource NrqlAlertCondition examples.
+        > **WARNING:** The `InfraAlertCondition` resource is deprecated and will be removed in the next major release. The resource NrqlAlertCondition would be a preferred alternative to configure alert conditions - in most cases, feature parity can be achieved with a NRQL query. For more details and examples on moving away from infra alert conditions to the NRQL based alternative, please check out these examples.
 
         ## Example Usage
 
@@ -753,7 +753,7 @@ class InfraAlertCondition(pulumi.CustomResource):
         """
         Use this resource to create and manage Infrastructure alert conditions in New Relic.
 
-        > **WARNING:** The `InfraAlertCondition` resource is deprecated and will be removed in the next major release. The resource NrqlAlertCondition examples.
+        > **WARNING:** The `InfraAlertCondition` resource is deprecated and will be removed in the next major release. The resource NrqlAlertCondition would be a preferred alternative to configure alert conditions - in most cases, feature parity can be achieved with a NRQL query. For more details and examples on moving away from infra alert conditions to the NRQL based alternative, please check out these examples.
 
         ## Example Usage
 

pulumi_newrelic/notification_channel.py

@@ -383,10 +383,12 @@ class NotificationChannel(pulumi.CustomResource):
                 {
                     "key": "project",
                     "value": "10000",
+                    "label": "Project-Name",
                 },
                 {
                     "key": "issuetype",
                     "value": "10004",
+                    "label": "Bug",
                 },
                 {
                     "key": "description",
@@ -586,7 +588,7 @@ class NotificationChannel(pulumi.CustomResource):
 
         More details about the channels API can be found [here](https://docs.newrelic.com/docs/apis/nerdgraph/examples/nerdgraph-api-notifications-channels).
         ### Moving from Legacy Alert Channels to Notification Channels
-        As described in the documentation of this resource, channels can be created and managed using `NotificationDestination`, which is **deprecated** and will be **removed in a future major release**, as stated in the documentation of the resource.
+        As described in the documentation of this resource, channels can be created and managed using `NotificationDestination` and `NotificationChannel`. A combination of these resources is an alternative to the legacy resource `AlertChannel`, which is **deprecated** and will be **removed in a future major release**, as stated in the documentation of the resource.
 
         If you're currently using `AlertChannel` to manage channels, we **strongly recommend** migrating to these notifications-based resources at the earliest.
 
@@ -725,10 +727,12 @@ class NotificationChannel(pulumi.CustomResource):
                 {
                     "key": "project",
                     "value": "10000",
+                    "label": "Project-Name",
                 },
                 {
                     "key": "issuetype",
                     "value": "10004",
+                    "label": "Bug",
                 },
                 {
                     "key": "description",
@@ -928,7 +932,7 @@ class NotificationChannel(pulumi.CustomResource):
 
         More details about the channels API can be found [here](https://docs.newrelic.com/docs/apis/nerdgraph/examples/nerdgraph-api-notifications-channels).
         ### Moving from Legacy Alert Channels to Notification Channels
-        As described in the documentation of this resource, channels can be created and managed using `NotificationDestination`, which is **deprecated** and will be **removed in a future major release**, as stated in the documentation of the resource.
+        As described in the documentation of this resource, channels can be created and managed using `NotificationDestination` and `NotificationChannel`. A combination of these resources is an alternative to the legacy resource `AlertChannel`, which is **deprecated** and will be **removed in a future major release**, as stated in the documentation of the resource.
 
         If you're currently using `AlertChannel` to manage channels, we **strongly recommend** migrating to these notifications-based resources at the earliest.