-
Notifications
You must be signed in to change notification settings - Fork 164
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
Automatically update haproxy image #32
Comments
It is a good idea! Maybe dependabot would be a good solution. @yajo? |
I'm using renovate myself so if you decide for that I could also provide some input. |
If you are willing to make a PR with a start, that would be good. |
I forked and activated renovate on my repo. It seems that renovate has a problem with how the image is specified in the Dockerfile. I have an idea of how to solve it, but I'll have to further look into it. Is
Otherwise I'll have to look up how to override the regex renovate is using to find the location of the image string. |
Ok, thank you. As for the |
We can't have such thing without good coverage. #34 is still more important IMHO. |
How about if we have nightly and stable versions? With this the user of the image could choose whether to always use the version with the latest haproxy or not. I ran into this again because there is currently a permission problem with this repo and the latest haproxy image. I think it would be great if I could fix the issue that I am having in here so everyone can profit. |
We now have the automation required for this to be acceptable. However, it's not our current priority. Community contributions welcome. |
It would be great to use something like renovate or dependabot to automatically update the haproxy image so security fixes in haproxy are applied instantly.
The text was updated successfully, but these errors were encountered: