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

[Bug]: ImageNameSubstitutor cannot set compatibility #9575

Open
Fleshgrinder opened this issue Nov 30, 2024 · 0 comments
Open

[Bug]: ImageNameSubstitutor cannot set compatibility #9575

Fleshgrinder opened this issue Nov 30, 2024 · 0 comments
Labels

Comments

@Fleshgrinder
Copy link

Fleshgrinder commented Nov 30, 2024

A custom ImageNameSubstitutor cannot be used to mark an image as compatible substitute for another image automatically, because all implementation I found call the compatibility assertion on their constructor argument, not on the image property from the parent class that actually applies the substitution.

I want to dynamically resolve images from a Dockerfile in the root of my project to allow Dependabot/Renovate to automatically update the images for me, and thus keep my tests up-to-date. For this I wanted to use short aliases and to set compatibility dynamically. However, this isn't possible for the reasons explained.

I'm filing this as a bug, because I believe that this isn't the intended behavior. Feel free to change this.

@Fleshgrinder Fleshgrinder changed the title [Bug]: [Bug]: ImageNameSubstitutor cannot be used to set compatibility Nov 30, 2024
@Fleshgrinder Fleshgrinder changed the title [Bug]: ImageNameSubstitutor cannot be used to set compatibility [Bug]: ImageNameSubstitutor cannot set compatibility Nov 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant