You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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 theenv.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
The text was updated successfully, but these errors were encountered: