pulumi-newrelic 5.31.0a1724997093__py3-none-any.whl → 5.31.1__py3-none-any.whl
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.
- pulumi_newrelic/_inputs.py +980 -0
- pulumi_newrelic/alert_channel.py +2 -2
- pulumi_newrelic/alert_policy_channel.py +2 -2
- pulumi_newrelic/api_access_key.py +12 -0
- pulumi_newrelic/cloud/aws_integrations.py +350 -1152
- pulumi_newrelic/infra_alert_condition.py +2 -2
- pulumi_newrelic/notification_channel.py +6 -2
- pulumi_newrelic/outputs.py +812 -0
- pulumi_newrelic/pulumi-plugin.json +1 -1
- pulumi_newrelic/synthetics/alert_condition.py +2 -2
- pulumi_newrelic/workflow.py +2 -2
- {pulumi_newrelic-5.31.0a1724997093.dist-info → pulumi_newrelic-5.31.1.dist-info}/METADATA +1 -1
- {pulumi_newrelic-5.31.0a1724997093.dist-info → pulumi_newrelic-5.31.1.dist-info}/RECORD +15 -15
- {pulumi_newrelic-5.31.0a1724997093.dist-info → pulumi_newrelic-5.31.1.dist-info}/WHEEL +1 -1
- {pulumi_newrelic-5.31.0a1724997093.dist-info → pulumi_newrelic-5.31.1.dist-info}/top_level.txt +0 -0
pulumi_newrelic/alert_channel.py
CHANGED
@@ -169,7 +169,7 @@ class AlertChannel(pulumi.CustomResource):
|
|
169
169
|
"""
|
170
170
|
Use this resource to create and manage New Relic alert channels.
|
171
171
|
|
172
|
-
> **WARNING:** The `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 `NotificationDestination` for a detailed illustration on setting up channels with these resources.
|
172
|
+
> **WARNING:** The `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 `NotificationDestination` and `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.
|
173
173
|
|
174
174
|
## Example Usage
|
175
175
|
|
@@ -317,7 +317,7 @@ class AlertChannel(pulumi.CustomResource):
|
|
317
317
|
"""
|
318
318
|
Use this resource to create and manage New Relic alert channels.
|
319
319
|
|
320
|
-
> **WARNING:** The `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 `NotificationDestination` for a detailed illustration on setting up channels with these resources.
|
320
|
+
> **WARNING:** The `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 `NotificationDestination` and `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.
|
321
321
|
|
322
322
|
## Example Usage
|
323
323
|
|
@@ -133,7 +133,7 @@ class AlertPolicyChannel(pulumi.CustomResource):
|
|
133
133
|
"""
|
134
134
|
Use this resource to map alert policies to alert channels in New Relic.
|
135
135
|
|
136
|
-
> **WARNING:** The `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 `Workflow` for a detailed illustration on setting up channels and workflows with these resources.
|
136
|
+
> **WARNING:** The `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 `Workflow`, with the channels to be mapped created using a combination of the newer resources `NotificationDestination` and `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.
|
137
137
|
|
138
138
|
## Example Usage
|
139
139
|
|
@@ -196,7 +196,7 @@ class AlertPolicyChannel(pulumi.CustomResource):
|
|
196
196
|
"""
|
197
197
|
Use this resource to map alert policies to alert channels in New Relic.
|
198
198
|
|
199
|
-
> **WARNING:** The `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 `Workflow` for a detailed illustration on setting up channels and workflows with these resources.
|
199
|
+
> **WARNING:** The `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 `Workflow`, with the channels to be mapped created using a combination of the newer resources `NotificationDestination` and `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.
|
200
200
|
|
201
201
|
## Example Usage
|
202
202
|
|
@@ -264,6 +264,12 @@ class ApiAccessKey(pulumi.CustomResource):
|
|
264
264
|
|
265
265
|
> **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).
|
266
266
|
|
267
|
+
## Extended Usage
|
268
|
+
|
269
|
+
This module may be used to create a user or ingest key using the `create_access_keys_service` resource, and fetch the created key using `fetch_access_keys_service`, by performing a NerdGraph query under the hood, using the ID of the key created via the resource to fetch the created key.
|
270
|
+
Please refer\\
|
271
|
+
create access keys and fetch access keys for more info.
|
272
|
+
|
267
273
|
## Import
|
268
274
|
|
269
275
|
Existing API access keys can be imported using a composite ID of `<api_access_key_id>:<key_type>`. `<key_type>`
|
@@ -309,6 +315,12 @@ class ApiAccessKey(pulumi.CustomResource):
|
|
309
315
|
|
310
316
|
> **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).
|
311
317
|
|
318
|
+
## Extended Usage
|
319
|
+
|
320
|
+
This module may be used to create a user or ingest key using the `create_access_keys_service` resource, and fetch the created key using `fetch_access_keys_service`, by performing a NerdGraph query under the hood, using the ID of the key created via the resource to fetch the created key.
|
321
|
+
Please refer\\
|
322
|
+
create access keys and fetch access keys for more info.
|
323
|
+
|
312
324
|
## Import
|
313
325
|
|
314
326
|
Existing API access keys can be imported using a composite ID of `<api_access_key_id>:<key_type>`. `<key_type>`
|