@pulumi/newrelic 5.31.0 → 5.32.0-alpha.1725688055
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/alertChannel.d.ts +1 -1
- package/alertChannel.js +1 -1
- package/alertPolicyChannel.d.ts +1 -1
- package/alertPolicyChannel.js +1 -1
- package/infraAlertCondition.d.ts +1 -1
- package/infraAlertCondition.js +1 -1
- package/notificationChannel.d.ts +1 -1
- package/notificationChannel.js +1 -1
- package/package.json +2 -2
- package/synthetics/alertCondition.d.ts +1 -1
- package/synthetics/alertCondition.js +1 -1
- package/workflow.d.ts +1 -1
- package/workflow.js +1 -1
package/alertChannel.d.ts
CHANGED
|
@@ -4,7 +4,7 @@ import * as outputs from "./types/output";
|
|
|
4
4
|
/**
|
|
5
5
|
* Use this resource to create and manage New Relic alert channels.
|
|
6
6
|
*
|
|
7
|
-
* > **WARNING:** The `newrelic.AlertChannel` resource is **deprecated** and will be **removed in a future major release**. As an alternative, you can set up channels using a combination of the newer resources `newrelic.NotificationDestination` for a detailed illustration on setting up channels with these resources.
|
|
7
|
+
* > **WARNING:** The `newrelic.AlertChannel` resource is **deprecated** and will be **removed in a future major release**. As an alternative, you can set up channels using a combination of the newer resources `newrelic.NotificationDestination` and `newrelic.NotificationChannel`. We **strongly recommend** migrating to these new resources at the earliest. Please refer to this example for a detailed illustration on setting up channels with these resources.
|
|
8
8
|
*
|
|
9
9
|
* ## Example Usage
|
|
10
10
|
*
|
package/alertChannel.js
CHANGED
|
@@ -8,7 +8,7 @@ const utilities = require("./utilities");
|
|
|
8
8
|
/**
|
|
9
9
|
* Use this resource to create and manage New Relic alert channels.
|
|
10
10
|
*
|
|
11
|
-
* > **WARNING:** The `newrelic.AlertChannel` resource is **deprecated** and will be **removed in a future major release**. As an alternative, you can set up channels using a combination of the newer resources `newrelic.NotificationDestination` for a detailed illustration on setting up channels with these resources.
|
|
11
|
+
* > **WARNING:** The `newrelic.AlertChannel` resource is **deprecated** and will be **removed in a future major release**. As an alternative, you can set up channels using a combination of the newer resources `newrelic.NotificationDestination` and `newrelic.NotificationChannel`. We **strongly recommend** migrating to these new resources at the earliest. Please refer to this example for a detailed illustration on setting up channels with these resources.
|
|
12
12
|
*
|
|
13
13
|
* ## Example Usage
|
|
14
14
|
*
|
package/alertPolicyChannel.d.ts
CHANGED
|
@@ -2,7 +2,7 @@ import * as pulumi from "@pulumi/pulumi";
|
|
|
2
2
|
/**
|
|
3
3
|
* Use this resource to map alert policies to alert channels in New Relic.
|
|
4
4
|
*
|
|
5
|
-
* > **WARNING:** The `newrelic.AlertPolicyChannel` resource is **deprecated** and will be **removed in a future major release**. As an alternative, you can map channels to policies using the resource `newrelic.Workflow` for a detailed illustration on setting up channels and workflows with these resources.
|
|
5
|
+
* > **WARNING:** The `newrelic.AlertPolicyChannel` resource is **deprecated** and will be **removed in a future major release**. As an alternative, you can map channels to policies using the resource `newrelic.Workflow`, with the channels to be mapped created using a combination of the newer resources `newrelic.NotificationDestination` and `newrelic.NotificationChannel`. We **strongly recommend** migrating to these new resources at the earliest. Please refer to this example for a detailed illustration on setting up channels and workflows with these resources.
|
|
6
6
|
*
|
|
7
7
|
* ## Example Usage
|
|
8
8
|
*
|
package/alertPolicyChannel.js
CHANGED
|
@@ -8,7 +8,7 @@ const utilities = require("./utilities");
|
|
|
8
8
|
/**
|
|
9
9
|
* Use this resource to map alert policies to alert channels in New Relic.
|
|
10
10
|
*
|
|
11
|
-
* > **WARNING:** The `newrelic.AlertPolicyChannel` resource is **deprecated** and will be **removed in a future major release**. As an alternative, you can map channels to policies using the resource `newrelic.Workflow` for a detailed illustration on setting up channels and workflows with these resources.
|
|
11
|
+
* > **WARNING:** The `newrelic.AlertPolicyChannel` resource is **deprecated** and will be **removed in a future major release**. As an alternative, you can map channels to policies using the resource `newrelic.Workflow`, with the channels to be mapped created using a combination of the newer resources `newrelic.NotificationDestination` and `newrelic.NotificationChannel`. We **strongly recommend** migrating to these new resources at the earliest. Please refer to this example for a detailed illustration on setting up channels and workflows with these resources.
|
|
12
12
|
*
|
|
13
13
|
* ## Example Usage
|
|
14
14
|
*
|
package/infraAlertCondition.d.ts
CHANGED
|
@@ -4,7 +4,7 @@ import * as outputs from "./types/output";
|
|
|
4
4
|
/**
|
|
5
5
|
* Use this resource to create and manage Infrastructure alert conditions in New Relic.
|
|
6
6
|
*
|
|
7
|
-
* > **WARNING:** The `newrelic.InfraAlertCondition` resource is deprecated and will be removed in the next major release. The resource newrelic.NrqlAlertCondition examples.
|
|
7
|
+
* > **WARNING:** The `newrelic.InfraAlertCondition` resource is deprecated and will be removed in the next major release. The resource newrelic.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.
|
|
8
8
|
*
|
|
9
9
|
* ## Example Usage
|
|
10
10
|
*
|
package/infraAlertCondition.js
CHANGED
|
@@ -8,7 +8,7 @@ const utilities = require("./utilities");
|
|
|
8
8
|
/**
|
|
9
9
|
* Use this resource to create and manage Infrastructure alert conditions in New Relic.
|
|
10
10
|
*
|
|
11
|
-
* > **WARNING:** The `newrelic.InfraAlertCondition` resource is deprecated and will be removed in the next major release. The resource newrelic.NrqlAlertCondition examples.
|
|
11
|
+
* > **WARNING:** The `newrelic.InfraAlertCondition` resource is deprecated and will be removed in the next major release. The resource newrelic.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.
|
|
12
12
|
*
|
|
13
13
|
* ## Example Usage
|
|
14
14
|
*
|
package/notificationChannel.d.ts
CHANGED
|
@@ -323,7 +323,7 @@ import * as outputs from "./types/output";
|
|
|
323
323
|
*
|
|
324
324
|
* More details about the channels API can be found [here](https://docs.newrelic.com/docs/apis/nerdgraph/examples/nerdgraph-api-notifications-channels).
|
|
325
325
|
* ### Moving from Legacy Alert Channels to Notification Channels
|
|
326
|
-
* As described in the documentation of this resource, channels can be created and managed using `newrelic.NotificationDestination`, which is **deprecated** and will be **removed in a future major release**, as stated in the documentation of the resource.
|
|
326
|
+
* As described in the documentation of this resource, channels can be created and managed using `newrelic.NotificationDestination` and `newrelic.NotificationChannel`. A combination of these resources is an alternative to the legacy resource `newrelic.AlertChannel`, which is **deprecated** and will be **removed in a future major release**, as stated in the documentation of the resource.
|
|
327
327
|
*
|
|
328
328
|
* If you're currently using `newrelic.AlertChannel` to manage channels, we **strongly recommend** migrating to these notifications-based resources at the earliest.
|
|
329
329
|
*
|
package/notificationChannel.js
CHANGED
|
@@ -327,7 +327,7 @@ const utilities = require("./utilities");
|
|
|
327
327
|
*
|
|
328
328
|
* More details about the channels API can be found [here](https://docs.newrelic.com/docs/apis/nerdgraph/examples/nerdgraph-api-notifications-channels).
|
|
329
329
|
* ### Moving from Legacy Alert Channels to Notification Channels
|
|
330
|
-
* As described in the documentation of this resource, channels can be created and managed using `newrelic.NotificationDestination`, which is **deprecated** and will be **removed in a future major release**, as stated in the documentation of the resource.
|
|
330
|
+
* As described in the documentation of this resource, channels can be created and managed using `newrelic.NotificationDestination` and `newrelic.NotificationChannel`. A combination of these resources is an alternative to the legacy resource `newrelic.AlertChannel`, which is **deprecated** and will be **removed in a future major release**, as stated in the documentation of the resource.
|
|
331
331
|
*
|
|
332
332
|
* If you're currently using `newrelic.AlertChannel` to manage channels, we **strongly recommend** migrating to these notifications-based resources at the earliest.
|
|
333
333
|
*
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@pulumi/newrelic",
|
|
3
|
-
"version": "5.
|
|
3
|
+
"version": "5.32.0-alpha.1725688055",
|
|
4
4
|
"description": "A Pulumi package for creating and managing New Relic resources.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"pulumi",
|
|
@@ -23,6 +23,6 @@
|
|
|
23
23
|
"pulumi": {
|
|
24
24
|
"resource": true,
|
|
25
25
|
"name": "newrelic",
|
|
26
|
-
"version": "5.
|
|
26
|
+
"version": "5.32.0-alpha.1725688055"
|
|
27
27
|
}
|
|
28
28
|
}
|
|
@@ -2,7 +2,7 @@ import * as pulumi from "@pulumi/pulumi";
|
|
|
2
2
|
/**
|
|
3
3
|
* Use this resource to create and manage synthetics alert conditions in New Relic.
|
|
4
4
|
*
|
|
5
|
-
* > **WARNING:** The `newrelic.synthetics.AlertCondition` resource is deprecated and will be removed in the next major release. The resource newrelic.NrqlAlertCondition example.
|
|
5
|
+
* > **WARNING:** The `newrelic.synthetics.AlertCondition` resource is deprecated and will be removed in the next major release. The resource newrelic.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 synthetics alert conditions to the NRQL based alternative, please check out this example.
|
|
6
6
|
*
|
|
7
7
|
* ## Example Usage
|
|
8
8
|
*
|
|
@@ -8,7 +8,7 @@ const utilities = require("../utilities");
|
|
|
8
8
|
/**
|
|
9
9
|
* Use this resource to create and manage synthetics alert conditions in New Relic.
|
|
10
10
|
*
|
|
11
|
-
* > **WARNING:** The `newrelic.synthetics.AlertCondition` resource is deprecated and will be removed in the next major release. The resource newrelic.NrqlAlertCondition example.
|
|
11
|
+
* > **WARNING:** The `newrelic.synthetics.AlertCondition` resource is deprecated and will be removed in the next major release. The resource newrelic.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 synthetics alert conditions to the NRQL based alternative, please check out this example.
|
|
12
12
|
*
|
|
13
13
|
* ## Example Usage
|
|
14
14
|
*
|
package/workflow.d.ts
CHANGED
|
@@ -145,7 +145,7 @@ import * as outputs from "./types/output";
|
|
|
145
145
|
* More details about the workflows can be found [here](https://docs.newrelic.com/docs/alerts-applied-intelligence/applied-intelligence/incident-workflows/incident-workflows/).
|
|
146
146
|
*
|
|
147
147
|
* ### Moving from Legacy Alert Policy Channels to Workflows
|
|
148
|
-
* As described in the documentation of this resource, mapping alert channels (created using `newrelic.NotificationDestination`).
|
|
148
|
+
* As described in the documentation of this resource, mapping alert channels (created using `newrelic.NotificationDestination` and `newrelic.NotificationChannel`) to policies can be performed using the `newrelic.Workflow` resource, which is an alternative to the legacy resource `newrelic.AlertPolicyChannel` (which consumes alert channels created using the legacy resource `newrelic.AlertChannel`).
|
|
149
149
|
*
|
|
150
150
|
* Both of the legacy resources mentioned above, `newrelic.AlertChannel` and `newrelic.AlertPolicyChannel` are **deprecated** and will be **removed in a future major release**, as stated in the documentation of both of these resources.
|
|
151
151
|
*
|
package/workflow.js
CHANGED
|
@@ -149,7 +149,7 @@ const utilities = require("./utilities");
|
|
|
149
149
|
* More details about the workflows can be found [here](https://docs.newrelic.com/docs/alerts-applied-intelligence/applied-intelligence/incident-workflows/incident-workflows/).
|
|
150
150
|
*
|
|
151
151
|
* ### Moving from Legacy Alert Policy Channels to Workflows
|
|
152
|
-
* As described in the documentation of this resource, mapping alert channels (created using `newrelic.NotificationDestination`).
|
|
152
|
+
* As described in the documentation of this resource, mapping alert channels (created using `newrelic.NotificationDestination` and `newrelic.NotificationChannel`) to policies can be performed using the `newrelic.Workflow` resource, which is an alternative to the legacy resource `newrelic.AlertPolicyChannel` (which consumes alert channels created using the legacy resource `newrelic.AlertChannel`).
|
|
153
153
|
*
|
|
154
154
|
* Both of the legacy resources mentioned above, `newrelic.AlertChannel` and `newrelic.AlertPolicyChannel` are **deprecated** and will be **removed in a future major release**, as stated in the documentation of both of these resources.
|
|
155
155
|
*
|