Skip to content

Commit

Permalink
Updated
Browse files Browse the repository at this point in the history
Updated the new changes
  • Loading branch information
mlakshmiharita committed Jan 17, 2025
1 parent f7055f8 commit 195a547
Showing 1 changed file with 1 addition and 4 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -30,10 +30,7 @@ You must do the following:

1. Go to [New Relic UI](https://docs.newrelic.com/docs/apis/intro-apis/new-relic-api-keys/) and determine which account you need a key for.

Check notice on line 31 in src/content/whats-new/2025/01/whats-new-03-01-rest-api-keys-eol.md

View workflow job for this annotation

GitHub Actions / vale

[vale] src/content/whats-new/2025/01/whats-new-03-01-rest-api-keys-eol.md#L31

[new-relic.ComplexWords] Consider using 'decide' or 'find' instead of 'determine'.
Raw output
{"message": "[new-relic.ComplexWords] Consider using 'decide' or 'find' instead of 'determine'.", "location": {"path": "src/content/whats-new/2025/01/whats-new-03-01-rest-api-keys-eol.md", "range": {"start": {"line": 31, "column": 97}}}, "severity": "INFO"}
2. Create new User API keys associated to that account.
3. Update your systems to use the new User API keys.

a. Go to [one.newrelic.com/api-keys](http://one.newrelic.com/api-keys) or [one.eu.newrelic.com/api-keys](http://one.eu.newrelic.com/api-keys) for EU data center and refer to the create and update instructions [here](https://docs.newrelic.com/docs/apis/intro-apis/new-relic-api-keys/#rotate-user-key).

3. Update your systems to use the new User API keys. Go to [one.newrelic.com/api-keys](http://one.newrelic.com/api-keys) or [one.eu.newrelic.com/api-keys](http://one.eu.newrelic.com/api-keys) for EU data center and refer to the create and update instructions [here](https://docs.newrelic.com/docs/apis/intro-apis/new-relic-api-keys/#rotate-user-key).
4. Ensure your API integrations function/work correctly with the new keys. This requires updating any scripts or code that reference the old key to use the new key value.
5. Once validated, remove the old REST API keys. After the old key is deleted, it cannot be restored.

Check notice on line 35 in src/content/whats-new/2025/01/whats-new-03-01-rest-api-keys-eol.md

View workflow job for this annotation

GitHub Actions / vale

[vale] src/content/whats-new/2025/01/whats-new-03-01-rest-api-keys-eol.md#L35

[Microsoft.Passive] 'is deleted' looks like passive voice.
Raw output
{"message": "[Microsoft.Passive] 'is deleted' looks like passive voice.", "location": {"path": "src/content/whats-new/2025/01/whats-new-03-01-rest-api-keys-eol.md", "range": {"start": {"line": 35, "column": 68}}}, "severity": "INFO"}

Check failure on line 35 in src/content/whats-new/2025/01/whats-new-03-01-rest-api-keys-eol.md

View workflow job for this annotation

GitHub Actions / vale

[vale] src/content/whats-new/2025/01/whats-new-03-01-rest-api-keys-eol.md#L35

[Microsoft.Contractions] Use 'can't' instead of 'cannot'.
Raw output
{"message": "[Microsoft.Contractions] Use 'can't' instead of 'cannot'.", "location": {"path": "src/content/whats-new/2025/01/whats-new-03-01-rest-api-keys-eol.md", "range": {"start": {"line": 35, "column": 83}}}, "severity": "ERROR"}

Check notice on line 35 in src/content/whats-new/2025/01/whats-new-03-01-rest-api-keys-eol.md

View workflow job for this annotation

GitHub Actions / vale

[vale] src/content/whats-new/2025/01/whats-new-03-01-rest-api-keys-eol.md#L35

[Microsoft.Passive] 'be restored' looks like passive voice.
Raw output
{"message": "[Microsoft.Passive] 'be restored' looks like passive voice.", "location": {"path": "src/content/whats-new/2025/01/whats-new-03-01-rest-api-keys-eol.md", "range": {"start": {"line": 35, "column": 90}}}, "severity": "INFO"}

Expand Down

0 comments on commit 195a547

Please sign in to comment.