generated from konveyor-ecosystem/template-repo
-
Notifications
You must be signed in to change notification settings - Fork 31
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
Rename PODMAN_BIN
to CONTAINER_TOOL
with backward compatibility
#168
Labels
good first issue
Good for newcomers
kind/feature
Categorizes issue or PR as related to a new feature.
priority/low
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Comments
This issue is currently awaiting triage. |
This issue has been marked 'good first issue' |
Hey, I issued a PR that might close this issue!! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
good first issue
Good for newcomers
kind/feature
Categorizes issue or PR as related to a new feature.
priority/low
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
This came up in #165: now that kantra will automatically fall back to
docker
ifpodman
isn't present,PODMAN_BIN
doesn't make quite as much sense. Renaming it toCONTAINER_TOOL
would help clarify what the override is actually overriding.Continuing to accept
PODMAN_BIN
and forwarding it toCONTAINER_TOOL
means this doesn't need to be a breaking change. (I don't mind if this is a breaking change myself, though, just an idea.)A name other than
CONTAINER_TOOL
is fine with me, it does seem like an easy pick though. I also took a look in k8s and see that name being used: https://github.com/search?q=org%3Akubernetes-sigs+CONTAINER_TOOL&type=codeThe text was updated successfully, but these errors were encountered: