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

allowing users to change parameters when exporting soopervisor #108

Open
edublancas opened this issue Aug 24, 2022 · 0 comments
Open

allowing users to change parameters when exporting soopervisor #108

edublancas opened this issue Aug 24, 2022 · 0 comments

Comments

@edublancas
Copy link
Contributor

A user is currently editing the generated Argo YAML spec to switch pipeline parameters (i.e., adding --env-param value) because the only way to change parameters currently is by switching the env.yaml but this implies re-building the docker image.

I think we have to replicate this behavior and study what the best solution is. On the one hand, I think if the only changed file in the project is the env.yaml, then, re-building and uploading the docker image will be fast but is still adding some overhead.

Alternatively, we can incorporate the --env parameter value feature in the CLI so it behaves more like the Ploomber CLI:

soopervisor export name --env--param value
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