You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
Fleshgrinder
changed the title
[Bug]:
[Bug]: ImageNameSubstitutor cannot be used to set compatibility
Nov 30, 2024
Fleshgrinder
changed the title
[Bug]: ImageNameSubstitutor cannot be used to set compatibility
[Bug]: ImageNameSubstitutor cannot set compatibility
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.
The text was updated successfully, but these errors were encountered: