[Platform Deprecations] Scope out the changes needed for 3rd-party-apps

[rudouglas]

Description

Schema properties are being deprecated.
Users of affected nerdlets should be notified 12 months in advance via warnings logged in the console of applications. Then 1 month before deprecation red error toasts are posted in the platform UI when the nerdlet is loaded.

This posts these toast messages for customers as well so there have been support tickets around them, as they've caused some confusion.

We will need to scope out the work needed on our end to alter or remove the affected properties. These are generally located in the nr1.json schema of a nerdlet.

Some examples are actionCategory being removed and entities changing to context.entities.

Example PR with changes:

newrelic/nr1-event-stream#59

Acceptance Criteria

• The work to implement the needed changes is scoped and ticketed
• Assess what changes need to be made to our workflow so we can address these in good time

[jpvajda]

References to when we did this before and some related issues:

newrelic/developer-website#1033
newrelic/developer-website#895

The ideal is we setup automation to automatically update the JS bundle for our SDK documentation and also automate the deprecation of components in the 3rd party app ecosystem.

[jpvajda]

I think now that we have a 2 month grace period we can look at this in the next sprint.

[rudouglas]

Example Issue created by the action rudouglas#2

@jpvajda Still TBD on this is how often this should run etc, at the moment it's triggered manually

I also need permissions to add secrets to the repo, both NR_QUERY_KEY ID and NR_ACCOUNT_ID are required for querying the data

[jpvajda]

@rudouglas nice, will this issue be sent this way to all repos where this is occuring? Or are you going to specifically customize the issue to relate to the repo?

For example: will I see this entire checklist of problems is all repos? I'd prefer if we just specified which problem exists in the specific repo.

[jpvajda]

We discussed how we'd actually determine when to run this job, and send notices to the repo maintainers to take action.

• use the event data provided to the platform to create an issue to the correct repo
• set up the job to run periodically
• other?

Other ideas:

• the deprecation issue is labeled with deprecations
• the issue is added to our GH 3rd party project board

[rudouglas]

@jpvajda at the moment it should just create a single issue in this repo (nr1-catalog) with a list of all apps and issues reported, if you would rather a separate issue in each repo that could be done pretty easily, slap a deprecation label on them and push them to the 3rd party project board

[jpvajda]

@rudouglas that single issue approach is great! How do we get notified this issue is created though since we don't spend a lot of time in that repo.

[rudouglas]

@jpvajda we could get it added to our Board would be the best way 🤷

[jpvajda]

@rudouglas this is the way ▶️