-
Notifications
You must be signed in to change notification settings - Fork 90
Add workflow to update images #1287
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
031b8c9 to
49442c0
Compare
49442c0 to
0c6239c
Compare
|
/hold until cc-utils is merged |
It's not required since the called workflow uses a GitHub App token with the necessary permissions.
|
This pull request introduces a new GitHub Actions workflow designed to automate the maintenance of container image versions. The workflow is configured to run on a weekly schedule, every Sunday, and can also be triggered manually. It utilizes a reusable workflow from the Walkthrough
Model: gemini-2.5-pro | Prompt Tokens: 387 | Completion Tokens: 155 |
PR1367 in cc-utils is merged now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
|
/unhold |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
How to categorize this PR?
/area dev-productivity
/kind enhancement
/platform azure
What this PR does / why we need it:
This PR corresponds to PR1367. It adds a GH Workflow to auto-update the
imagevector/images.yamlfile. It makes use of a re-usable GH Workflow and a corresponding GH Action that's added to the cc-utils repo in PR1367 that can be used in othergardener-extension-provider-<provider>repos as well.The resulting changes in
imagevector/images.yamlare commited and a PR is created automatically. Within the PR, a list of all the updated image versions is given with links to the respective release notes. This list includes intermediate releases. All the links have to be checked by a developer/reviewer for possible breaking changes. To ensure this, a checklist is added to the PR.Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
I guess a better solution would be to change everything to update based on OCM. Therefor this PR is considered a intermediate step to already provide some automation without the effort to implement the final version.
Release note: