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
In ArgoCD 2.5, it appears currently if you define a server url in a project definition, you must use server URL in all application manifests. If you define a server name in a project, you must use the project name. You cannot define server urls in a project definition and then use the server name in the application manifest.
I had thought you couldn't define projects using server names until I saw this PR: #11706. Then ran into issues trying to migrate some projects and apps with permission denied unless I updated the project with both server URL and Name at the same time until I have a chance to migrate the app definitions.
Motivation
Make it easier to define RBAC.
Proposal
ArgoCD should resolve both server URL and name when checking project RBAC rules so that users can use either value.
The text was updated successfully, but these errors were encountered:
Summary
In ArgoCD 2.5, it appears currently if you define a server url in a project definition, you must use server URL in all application manifests. If you define a server name in a project, you must use the project name. You cannot define server urls in a project definition and then use the server name in the application manifest.
I had thought you couldn't define projects using server names until I saw this PR: #11706. Then ran into issues trying to migrate some projects and apps with permission denied unless I updated the project with both server URL and Name at the same time until I have a chance to migrate the app definitions.
Motivation
Make it easier to define RBAC.
Proposal
ArgoCD should resolve both server URL and name when checking project RBAC rules so that users can use either value.
The text was updated successfully, but these errors were encountered: