Changing how upstream sync works as part of devsecops #17
JayGhiya
announced in
Announcements
Replies: 1 comment 1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Currently we have a alpha workflow which fetches latest charts of stateful applications as stated below:
actions/checkout@v2
action and specify theupstream-sync
branch.azure/setup-helm@v3
action and specify versionv3.11.1
.yq
.docker/login-action@v2
action.github/codeql-action/upload-sarif@v2
action.charts
andreports
folders, then pushing to theupstream-sync
branch.peter-evans/create-pull-request@v3
action with specified title, commit message, branch, base, and token.The problem with the current approach is that we are using same static branch for fetching updates and raising pr with develop branch.
Here is a major downside to it:
The alternative solution is to run the batch job always with a new branch named "upstream-sync-$helm-chart-version". Also while fetching pr it has to check whether chart version is really updated compared to last to avoid duplicates. This should make the process clean. Share your thoughts on the same. Will share updated action soon.
Beta Was this translation helpful? Give feedback.
All reactions