Remove the use of the Catalog Manager and automate versioning updates of nerdpacks

jpvajda commented 3 years ago

Relates to #8

References

https://github.com/newrelic/nr1-catalog/wiki/New-Relic-One-App-Catalog-How-To-Guide

Preliminary

[ ] Evaluate if the Catalog manager is something we need for our nerdpack version deployment needs longer term as it could make more sense to invest in putting in automation where a repo action would actually deploy the version update directly to the catalog, and remove the need for the catalog manager all together.

We propose making improvements to workflow:

[ ] When an application is updating and versioned, we automatically run App Catalog Update checks on that app's GH repo on build and deployment to main.
[ ] If these checks pass, we kick off a PR to the NR1-Catalog repo to update the application's version in the US:Prod.
[ ] We then review the PR and merge it in, thus updating the app WITHOUT the use of the catalog manager.
[ ] We no longer use the catalog manager to these updates, so we'll want to move this project to either experimental or archived it's currently set to community.
[ ] Some of these changes may impact the Catalog repo

jpvajda commented 3 years ago

We may not want to support the catalog manager longer term, so perhaps we don't want do this.

jpvajda commented 3 years ago

@zstix I updated this ticket and also really read the AC closely 🤣 it's more about removing the catalog manager from the deployment flow, vs trying to improve it, so it could be good work to take on.

jpvajda commented 3 years ago

@jbeveland27 / @devfreddy just curious if we were to remove the use of the catalog manager from the deployment of nerdpack versions and instead just had a repo action to kick off a version update to the catalog repo, would that be an approach you'd have any concerns with? I know you all spent some time creating the catalog manager, but we are just considering ways to automate this process. We do realize that staging and EU still need manual deploys. I've documented the process as it is today here for reference: https://github.com/newrelic/nr1-catalog/wiki/New-Relic-One-App-Catalog-How-To-Guide

jbeveland27 commented 3 years ago

@jpvajda Should work fine. Would just need to communicate to the various stakeholders(mostly the maintainers of the repos) that PRs to the Catalog are now automatic.

The catalog workflow that's used by the Catalog Manager can even be mostly reused, you'll just need to modify it to run when a release is made and make sure the appropriate variables are populated.

newrelic / nr1-catalog-manager