-
Notifications
You must be signed in to change notification settings - Fork 699
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
Add support for custom image labels #601
Conversation
looks reasonable to me. i don't think s2i should be concerned w/ the autogeneration aspect, we should handle that in origin and just set explicit label values in the s2i config object when invoking s2i. |
@bparees I was thinking that some of the generated labels may have to be generated on the s2i side because openshift doesn't have the cloned repository. Now I see that cloning is done in openshift code so it shouldn't be a problem to access all the information about a repository. Should I extend this PR with a means to disable the label generation as currently implemented in s2i or is it out of scope of the trello card? |
Out of scope. We need to leave that in place anyway for compatibility for Ben Parees | OpenShift On Oct 4, 2016 6:24 AM, "Martin Milata" notifications@github.com wrote:
|
LGTM, good job with adding more tests :-) |
[merge] |
Evaluated for source to image merge up to e3d70cb |
Source To Image Merge Results: SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_sti/251/) |
Needed for https://trello.com/c/HB9IwGj5/925-5-add-arbitrary-labels-to-docker-images
Work in progress because we probably need to discuss how the API should look like in order to support autogenerated values (e.g. SCM commit hash) in the future.