Make multiple different Argo CD projects using a single repository

[d7volker]

Summary

The developers should be able to define the repositories on their own. That is why we use scoped repositories in this case. Now it can happen that developers out of two different Argo CD projects use the same repository even with different repository credentials. As you know it is impossible to define a repository twice. I would say it is a problem for us that a repo can't be defined twice or more times. As I understood you use the repo URL as the key to refer to it.

Why it is not possible to use the repo URL and the Argo CD project it is bound to as a key?

Are there other possibilities to achieve that two different Argo CD projects use same repository without bother the admins of Argo CD? For example with a dedicated RBAC rule?

Motivation

That would also be of help in the following: Imaging a Argo CD project which is able to deploy its code on development and integration but not on production. The deployment on to production will be handled by a different Argo CD project using the same repository as the developers in the first project.

Proposal

As I understood you use the repo URL as the key to refer to it.
Why it is not possible to use the repo URL and the Argo CD project it is bound to as a key?

[m-yosefpor]

We have the same problem and it is causing many troubles for devs. Also I think the project of each repo should be showed in argocd UI (setting > repositories).

[crenshaw-dev]

I think a lot of Argo CD code assumes that a repo (of a given URL) is a repo. I agree, we should provide a mechanism to use the same repo using different credentials. It would take some work on the backend, but should be possible.

[alemnew]

Has there been any update on this? I also got this issue, and wouldn't appreciate if there has been a mechanism.

[dario-lab]

Hi,
I have an issue where:

1. I added via UI repository to the project: Project1 HELM: helm.repo.io and this repository is working properly.
   After it I tried add the same repository to the Project-2, but I have an issue:
   Unable to connect HTTPS repository: existing repository spec is different; use upsert flag to force update; difference in keys "Name,Project"

What can i do to use the same repository in many projects?

[acuD1]

Hi,

Just encountered this behavior. We're splitting our environments with Project. As we use the same repository with Helm in front, I can't.

Regards.

[pazfelipe]

Any updates? I've been facing the same issue already mentioned here
Unable to connect HTTPS repository: existing repository spec is different; use upsert flag to force update...

[lacrimal]

Is it idea similar to Google Anthos multi-repo ?
I'm looking something similar in argo-cd and stuck, at beginning was getting this feature obvious.

[FsRiachos]

Hi there,

since there any update to the issue is there any workaround?

Thank you

[manali14]

Hi,

Is there a workaround that people are using for this?

[m-yosefpor]

You can use global repos and limit access with approj (the old way). Though this renders the whole point of scoped repositories useless

[SakaYK]

as mentioned by m-yosefpor, you can use global repo and chose the repository in the project.
i'm using this method since v2.4.8, to use the same helm repository in multiple project environment.

1. Go to repositories menu and create helm repository connection but don't attach it to any project.
2. Create/Edit your project, Find the SOURCE REPOSITORIES and click the edit button., and chose the helm repository that you create earlier.
3. Repeat Step-2.

[yyzxw]

Hi, is there any way to make different appProject contain different repository, or the same repoURL can have different credentials, for example, the same repoURL can create different Argocd applications in the same repository but different directories, or any workaround?

Thank you

[ahmadalkhansa]

Hi, is there going to be modifications to the management of git repository connections? It would create conflict and confusion among users that have access to separate projects and would like to connect to the same repositories.

[blakepettersson]

Hi, see #18290 - let me know what you think

[blakepettersson]

Reopening since that was the spec that got merged, not the actual implementation :)