You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Every time the backstage ArgoCD plugin is invoked it must create a new ArgoCD "AppProject".
This goes against how many (most?) organizations build out their Argo CD architecture. An "AppProject" often is used as a way to logically organize groups of Argo CD "Applications". However, it is rare that all of these "Applications" are created at the exact same time.
The plugin should be able to take an existing "AppProject" name as a parameter and simply use this if it already exists, and only create a new "AppProject" if it doesn't.
Possible Implementation
N/A
Context
We'd like to be able to use the plugin, but not have a new AppProject every time it runs.
Thank you!
The text was updated successfully, but these errors were encountered:
Feature Suggestion
Every time the backstage ArgoCD plugin is invoked it must create a new ArgoCD "AppProject".
This goes against how many (most?) organizations build out their Argo CD architecture. An "AppProject" often is used as a way to logically organize groups of Argo CD "Applications". However, it is rare that all of these "Applications" are created at the exact same time.
The plugin should be able to take an existing "AppProject" name as a parameter and simply use this if it already exists, and only create a new "AppProject" if it doesn't.
Possible Implementation
N/A
Context
We'd like to be able to use the plugin, but not have a new AppProject every time it runs.
Thank you!
The text was updated successfully, but these errors were encountered: