Support Branch Pattern for ImageUpdateAutomation #3135
Replies: 2 comments
-
I think there is only one way to do this right now, and it's what you already hinted at, multiple ImageUpdateAutomation resources, one for each app. Hopefully we can revisit these APIs after General Availability so that we can make them more flexible and easier to use in the future! |
Beta Was this translation helpful? Give feedback.
-
We have a similar setup and would appreciate dynamic branch names for image update automations. 👍🏼 Here's our setup: Currently, flux pushes observed version increments to a branch, a merge request is automatically generated (no Github Action, since we are on GitLab, i.e. a custom CI script) which we manually merge. Since this covers different apps, it would be great to divide the updates into update branches per app to have full flexibility in choosing which version increments to deploy to production. |
Beta Was this translation helpful? Give feedback.
-
Hi Folks, not sure if this is a question or a proposal, lets see:
I currently have Image Automation set up and its working well, pushes change to a new branch and a GitHub Action creates a PR. the issue with my current design is that if another image updates (from the same setters path but a different image) before the PR is closed the new change is pushed to the same branch and as such included in the same PR.
Is it possible to do something like branch: mybranch-$random so that each image update pushes to a different branch that follows some pattern?
Maybe however, this is the wrong flow and I should create an ImageUpdateAutomation for each app independently? Currently I have something like:
Beta Was this translation helpful? Give feedback.
All reactions