pulumi-newrelic 5.31.0a1724997093__py3-none-any.whl → 5.31.0a1725491574__py3-none-any.whl

pulumi_newrelic/api_access_key.py

@@ -264,6 +264,12 @@ class ApiAccessKey(pulumi.CustomResource):
 
         > **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).
 
+        ## Extended Usage
+
+        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.
+        Please refer\\
+        create access keys and fetch access keys for more info.
+
         ## Import
 
         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):
 
         > **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).
 
+        ## Extended Usage
+
+        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.
+        Please refer\\
+        create access keys and fetch access keys for more info.
+
         ## Import
 
         Existing API access keys can be imported using a composite ID of `<api_access_key_id>:<key_type>`. `<key_type>`

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",
@@ -725,10 +727,12 @@ class NotificationChannel(pulumi.CustomResource):
                 {
                     "key": "project",
                     "value": "10000",
+                    "label": "Project-Name",
                 },
                 {
                     "key": "issuetype",
                     "value": "10004",
+                    "label": "Bug",
                 },
                 {
                     "key": "description",