Replies: 1 comment
-
The Pull Request generator exists precisely for this scenario https://argo-cd.readthedocs.io/en/latest/operator-manual/applicationset/Generators-Pull-Request/ Have you seen it? Full example here https://github.com/kostis-codefresh/preview-env-manifests/blob/main/argocd/smart-pr-generator.yml |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Consider a simple mono-repo for application manifests:
apps/
contains the configuration for bespoke apps, their source code is kept in separate repositories.app-of-apps/
contains theApplication
manifests for the apps inapps/
.Now let's assume that a developer makes a pull request against
apps/team-a/app1-a
while working on the source code for app1-a.It would be nice if the
targetRevision
of app1-a indev
automatically jumped to the pull request branch, and returned to it's default (eg.main
) after the pull request is closed.I can think of a couple of ways to do this, but they all have drawbacks / don't feel very elegant:
app-of-apps/dev/.argocd-source-<appname>.yaml
via CIApplication
patching via CIHow would you do it?
Beta Was this translation helpful? Give feedback.
All reactions