Merge pull request #18958 from newrelic/daily-release/Oct-14-2024-4_05

Daily release/oct 14 2024 4 05
newrelic · Oct 14, 2024 · b6be5b2 · b6be5b2
2 parents e02b8de + 454df8c
commit b6be5b2
Show file tree

Hide file tree

Showing 29 changed files with 1,608 additions and 1,499 deletions.
diff --git a/...nt/docs/apis/nerdgraph/examples/use-nerdgraph-manage-license-keys-user-keys.mdx b/...nt/docs/apis/nerdgraph/examples/use-nerdgraph-manage-license-keys-user-keys.mdx
@@ -53,10 +53,18 @@ To create multiple keys (user key or license key) in a single mutation, for mult
 
 Example of creating a key:
 
-```
+```graphql
 mutation {
-  apiAccessCreateKeys(keys: {ingest: {accountId: YOUR_ACCOUNT_ID, ingestType:
-    BROWSER, name: "Browser Key", notes: "A note."}}) {
+  apiAccessCreateKeys(
+    keys: {
+      ingest: {
+        accountId: YOUR_ACCOUNT_ID
+        ingestType: BROWSER
+        name: "Browser Key"
+        notes: "A note."
+      }
+    }
+  ) {
     createdKeys {
       id
       key
@@ -91,9 +99,16 @@ Here's an example of using this query to create a [user key](/docs/apis/get-star
   >
     To create a [user key](/docs/apis/get-started/intro-apis/types-new-relic-api-keys#user-api-key), you'd change the above query slightly, in the `keys` section:
 
-    ```
+    ```graphql
     mutation {
-      apiAccessCreateKeys(keys: {user: {accountId: YOUR_ACCOUNT_ID, userId: YOUR_USER_ID}}) {
+      apiAccessCreateKeys(
+        keys: { 
+          user: { 
+            accountId: YOUR_ACCOUNT_ID, 
+            userId: YOUR_USER_ID 
+          }
+        }
+      ) {
         createdKeys {
           id
           key
@@ -123,10 +138,17 @@ Here's an example of using this query to create a [user key](/docs/apis/get-star
 
 The update mutation takes the key ID, not the key string, to identify keys.
 
-```
+```graphql
 mutation {
-  apiAccessUpdateKeys(keys: {ingest: {keyId: KEY_ID, name: "Updated name", notes:
-    "A new note!"}}) {
+  apiAccessUpdateKeys(
+    keys: {
+      ingest: { 
+        keyId: KEY_ID, 
+        name: "Updated name", 
+        notes: "A new note!" 
+      }
+    }
+  ) {
     updatedKeys {
       id
       key
@@ -147,9 +169,9 @@ Results will vary depending on your data. Use the [GraphiQL explorer](https://ap
 
 The delete mutation takes the key ID, not the key string, to identify keys. Deleted keys will no longer grant access to New Relic systems and will no longer be returned by queries to the API access GraphQL API.
 
-```
+```graphql
 mutation {
-  apiAccessDeleteKeys(keys: {ingestKeyIds: INGEST_KEY_ID}) {
+  apiAccessDeleteKeys(keys: { ingestKeyIds: INGEST_KEY_ID }) {
     deletedKeys {
       id
     }
@@ -168,7 +190,7 @@ You can access ingest and user keys by querying a single key or all keys, scoped
 
 Single key example query:
 
-```
+```graphql
 query {
   actor {
     apiAccess {
@@ -187,11 +209,16 @@ query {
 
 Key search example query:
 
-```
+```graphql
 query {
   actor {
     apiAccess {
-      keySearch(query: {types: INGEST, scope: {ingestTypes: BROWSER}}) {
+      keySearch(query: { 
+        types: INGEST, 
+        scope: { 
+          ingestTypes: BROWSER 
+        } 
+      }) {
         keys {
           name
           key