Fardin Khanjani

In my case, the problem was that only the ArgoCD server (`argocd-server` pod) had access to the IAM role. It turns out that the application controller (`argocd-application-controller` pod) also needs...

My use case: In Production, only the main/master branch can be deployed. In Testing, a PR/branch can be deployed as well. It would be nice if ApplicationSet controller could optionally...

Another use case is when some teams would like to have auto-sync enabled on their application and some other teams prefer to sync manually.

Waiting for https://github.com/argoproj/applicationset/pull/472 to be merged.

@rishabh625 Please feel free to move this PR over to argocd repo. I should have some time to get back at this pretty soon. Thanks :)

A better alternative: Change the Pull Request generator to accept a pattern/regex for `repo` attribute, and if left empty it should find all the repos. Using this in conjunction with...

The above alternative is probably a good enhancement to the Pull Request generator in general. But embedding the Pull Request generator into the SCM generator has the added benefit of...

@jgwest Would love your thoughts before I start working on this :)

> @fardin01 how would you feel about adding templating support to the second generator in a matrix generator? Basically pass each variable set produced by the first generator to the...

A fix is being worked on in https://github.com/argoproj/applicationset/pull/511.