Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Project destinations should resolve both name and url without explicitly defining them #11962

Open
sidewinder12s opened this issue Jan 12, 2023 · 2 comments
Labels
enhancement New feature or request

Comments

@sidewinder12s
Copy link

sidewinder12s commented Jan 12, 2023

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.

@sidewinder12s sidewinder12s added the enhancement New feature or request label Jan 12, 2023
@sidewinder12s
Copy link
Author

Potentially related: #7198

It appears the issue is just in RBAC.

@cilindrox
Copy link
Contributor

Happening with ApplicationSets - seems the issue mentioned above solved this for Applications

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants