-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Introduce the quarkus.container-image.image property #12070
Conversation
I won't comment on the code but I think we need the particular GitLab case to be fully documented. |
Yeah that makes sense. I'll do that after I fix the actual test failures :) |
This property is meant to specify the entire image string as one would use on the docker command line or as is found in CI systems like GitLab (whose CI_REGISTRY_IMAGE) was used as a model for this Fixes: quarkusio#8588
Use ContainerImageInfoBuildItem wherever possible instead of using ContainerImageConfig
Tests fixed and doc added |
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
/** | ||
* This is basically a simplified version of {@code com.google.cloud.tools.jib.api.ImageReference} | ||
*/ | ||
public class ImageReference { |
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.
+1 we might want to replace our ImageUtils with that.
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.
Good idea!
Let's do that in a follow up. Perhaps the PR you are working on that reworks S2I?
Fixes: #8588
Also, clean up some technical debt related to the container-image extensions.
The handling of the image string and its parts is now much more consistent
between extensions