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
Right now, devel-up just always redefines parameters from scratch. This has the advantage that (1) going back to a default value just means dropping the corresponding switch and (2) you can be sure what config your pipeline is running with; the CLI invocation fully describes it.
OTOH, devel-up could be "stateful" so that options only define changes from the current state. In this scenario, going back to a default value would mean explicitly passing that switch. The advantage is that it's less verbose and easier to modify specific values. The disadvantage is that it's no longer as easy to keep track of what settings your pipeline is running with (e.g. we'd probably want a --view option or something).
Although I do see the appeal, I still overall favour the status quo myself for its simplicity and explicitness.
The text was updated successfully, but these errors were encountered:
Right now,
devel-up
just always redefines parameters from scratch. This has the advantage that (1) going back to a default value just means dropping the corresponding switch and (2) you can be sure what config your pipeline is running with; the CLI invocation fully describes it.OTOH,
devel-up
could be "stateful" so that options only define changes from the current state. In this scenario, going back to a default value would mean explicitly passing that switch. The advantage is that it's less verbose and easier to modify specific values. The disadvantage is that it's no longer as easy to keep track of what settings your pipeline is running with (e.g. we'd probably want a--view
option or something).Although I do see the appeal, I still overall favour the status quo myself for its simplicity and explicitness.
The text was updated successfully, but these errors were encountered: