Skip to content
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

Implement Enhanced Auto Bumper for Image Updates #12153

Open
5 tasks
Tracked by #10076
KacperMalachowski opened this issue Oct 16, 2024 · 0 comments
Open
5 tasks
Tracked by #10076

Implement Enhanced Auto Bumper for Image Updates #12153

KacperMalachowski opened this issue Oct 16, 2024 · 0 comments
Labels
area/tools Issues or PRs related to overall changes in tools Epic

Comments

@KacperMalachowski
Copy link
Contributor

KacperMalachowski commented Oct 16, 2024

Description

We aim to implement an enhanced auto bumper tool that will automatically detect and update image URLs in .yaml, .yml, Terraform configurations (.tf), and GitHub Actions/workflows. This tool can leverage existing functionality from our image-detector tool to simplify the process.

Reasons

Currently, we utilize the bumper implementation from the Kubernetes (k8s) team. However, this implementation is primarily designed for updating Prow and Kubernetes manifests and does not fully meet our requirements. An enhanced auto bumper will broaden the scope of automatic updates, ensure consistency, and minimize manual interventions.

This enhanced auto bumper will streamline our image update process, ensuring that all relevant configuration files are consistently updated, thus improving the overall quality and efficiency of our automated workflows.

Acceptance Criteria

  • Evaluate if tools like Dependabot or Renovate can be configured for our use case (e.g., Renovate Terraform module).
  • Develop a custom mechanism to bump images in .yaml, .yml, .tf (Terraform configurations), and GitHub Actions/workflows.
  • Ensure the solution does not require a config file listing specific files. Images should be bumped in all detected files from the root of the repository.
  • The solution must support both github.com and GitHub Enterprise Server.
  • The solution should be capable of running within a GitHub workflow.

Attachments

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/tools Issues or PRs related to overall changes in tools Epic
Projects
None yet
Development

No branches or pull requests

2 participants