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
similar to #9581 , support same repository address in different projects.
Motivation
we used ArgoCD as the backend engine for GitOps, and in a multi-tenant scenario, we isolated different projects as tenants. So we want different projects to save the same url, because even with the same url, their credentials may be different. or just distinguish by project.
why don't we use project and url as the key to create and query.
repo connection state
as mentioned above, the same URL may use different credentials, so also need to get the connection status of the repository for each project and url as the cache key.
Summary
similar to #9581 , support same repository address in different projects.
Motivation
we used ArgoCD as the backend engine for GitOps, and in a multi-tenant scenario, we isolated different projects as tenants. So we want different projects to save the same url, because even with the same url, their credentials may be different. or just distinguish by project.
Proposal
why don't we use
project
andurl
as the key to create and query.as mentioned above, the same URL may use different credentials, so also need to get the connection status of the repository for each
project
andurl
as the cache key.add
project
field. but there seems to be too much duplication with the repo definition. maybe it can be removed.use
default
project as default project if user not select project, is also for compatibility.query repo list need add
project
as query paramrepo cache key format:
Or if there's any way to do that, please let me know. Thank you!
If this proposal is acceptable, I will submit a PR for it.
The text was updated successfully, but these errors were encountered: