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

Support environment variables as input method for pipeline arguments #135

Open
Tristan971 opened this issue May 15, 2023 · 0 comments
Open

Comments

@Tristan971
Copy link

Tristan971 commented May 15, 2023

Title. Can't find another issue about it, so maybe it wasn't asked before? (seems unlikely but idk)

Especially when dealing with docker images it's significantly easier to work with environment variables than command arguments, due to how ENTRYPOINT + CMD + arguments work together being somewhat inconsistent from runtime to runtime.

Seems like argparse (which is the method used here afaik) doesn't natively handle environment variables for some reason; I do quite like this approach as a way to do it, although there are a few other methods.

I'd happily make a PR, but I figured I'd just suggest it first in case it's been asked and rejected before (but not on Github so I couldn't find it with a search).
Worst case scenario if it's unwanted, the next person to think about this sees this issue and can directly know so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant