The ApplicationSet controller manages multiple Argo CD Applications as a single ApplicationSet unit, supporting deployments to large numbers of clusters, deployments of large monorepos, and enabling secure Application self-service.
I was looking to have SCM generator discover repos in my organization that have a specific folder "k8s", then combine with Git generator to discover folders and generate one Application for each folder.
Consider two repos as follow:
Repo A
k8s
--- api
--- job-a
Repo B
k8s
--- web
--- api
So it would find both repos as both have the k8s folder, then create 4 applications (one for each subfolder).
Notice how in the Git generator I'm trying to use {{ url }} and {{ branch }} found by the SCM generator.
I thought this was implemented in #530 but I'm not sure that's the case, at least this is not working for me, and in the Matrix docs there is an example of combining Git + Cluster generators, but I don't really see the cluster generator referencing parameters from the Git generator, perhaps I misunderstood how it works.
Another solution would be just making SCM provider to support finding multiple paths (similar to Git generator), then there would be no need to use matrix generator.
I was looking to have SCM generator discover repos in my organization that have a specific folder "k8s", then combine with Git generator to discover folders and generate one Application for each folder.
Consider two repos as follow:
Repo A k8s --- api --- job-a
Repo B k8s --- web --- api
So it would find both repos as both have the k8s folder, then create 4 applications (one for each subfolder).
So I could create an ApplicationSet as below:
Notice how in the Git generator I'm trying to use {{ url }} and {{ branch }} found by the SCM generator.
I thought this was implemented in #530 but I'm not sure that's the case, at least this is not working for me, and in the Matrix docs there is an example of combining Git + Cluster generators, but I don't really see the cluster generator referencing parameters from the Git generator, perhaps I misunderstood how it works.
Thanks!