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

Should devel-up maintain state? #65

Closed
jlebon opened this issue Jun 5, 2019 · 1 comment
Closed

Should devel-up maintain state? #65

jlebon opened this issue Jun 5, 2019 · 1 comment

Comments

@jlebon
Copy link
Member

jlebon commented Jun 5, 2019

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.

@jlebon
Copy link
Member Author

jlebon commented Jun 20, 2022

I don't think this is worth changing at this point.

@jlebon jlebon closed this as not planned Won't fix, can't repro, duplicate, stale Jun 20, 2022
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