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
Hello,
My name is Archyl, and I am a Lead DevOps Engineer. On my current project, we use ArgoCD. I am looking for a solution to protect any ArgoCD application in my project from manual changes through the UI by the "QA" or "Developers" teams, except for the ArgoCD application version.
The main goal is to configure RBAC settings to provide the "QA" team with the ability to change only the "targetRevision:" field and sync it in any ArgoCD application, instead of providing full access to a specific project or ArgoCD applications.
Thanks in advance for your assistance!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello,
My name is Archyl, and I am a Lead DevOps Engineer. On my current project, we use ArgoCD. I am looking for a solution to protect any ArgoCD application in my project from manual changes through the UI by the "QA" or "Developers" teams, except for the ArgoCD application version.
The main goal is to configure RBAC settings to provide the "QA" team with the ability to change only the "targetRevision:" field and sync it in any ArgoCD application, instead of providing full access to a specific project or ArgoCD applications.
Thanks in advance for your assistance!
Beta Was this translation helpful? Give feedback.
All reactions