Hi all 👋

We already released the addon-framework where we want to provide out-of the box integrations with third party tools. It would be super helpful if someone familiar with New Relic could assist on building the New Relic integration. The idea is to inform New Relic about changes via [New Relic Custom events](https://docs.newrelic.com/docs/telemetry-data-platform/ingest-apis/introduct

Summary

The output of the status command is different if we run status with the --watch flag set to true or false. I am not sure if it was designed in that way, but for me, it is a bit confusing. Let's compare:

kubectl-argo-rollouts status example-spring-boot-prod-01 --namespace test-argo-prod --watch=true
Paused - BlueGreenPause
kubectl-argo-rollouts status example-spring-boot-prod

Requirements

Add an environment parameter in the config.
This environment field should be added to all users in the param so we can add rules based on the environment and have the same config file for all your environment.

Right now, when you archive a key, you can only see it if you manually search for it.

This can cause some key name conflict issues, or issues when trying to create a folder with the same name as an archived (bu not yet deleted key).

It would be ideal for there to be a way to see all archived keys at once, without the need to search for them in the search bar.