-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
safe Dvcfile.dump()
#4235
Labels
enhancement
Enhances DVC
p1-important
Important, aka current backlog of things to do
refactoring
Factoring and re-factoring
Comments
@skshetry Is this something that you are tackling right now(judging by the assignee)? If not, could you please elaborate a bit more? Also, please feel free to set appropriate labels. |
I'm not working right now, but something that I'd like to tackle next. |
@skshetry What about labels then? |
skshetry
added a commit
to skshetry/dvc
that referenced
this issue
Sep 8, 2020
The API of `Dvcfile.dump` has been changed to `dump(stage, update_pipeline=True, update_lock=True)`, which will make it to always dump by default to both files, and provide flags to suppress one or the other. Fixes iterative#4235
2 tasks
skshetry
added a commit
that referenced
this issue
Sep 10, 2020
The API of `Dvcfile.dump` has been changed to `dump(stage, update_pipeline=True, update_lock=True)`, which will make it to always dump by default to both files, and provide flags to suppress one or the other. Fixes #4235
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
enhancement
Enhances DVC
p1-important
Important, aka current backlog of things to do
refactoring
Factoring and re-factoring
Initially, the idea was not to touch
dvc.yaml
at all, but as we are doing it quite often, it's better to protectdvc.lock
rather thandvc.yaml
by default.So, we could change it to the following default:
The only place where we need to update
lock
aredvc repro
anddvc run
, at least atm.Originally posted by @skshetry in #3994 (comment)
The text was updated successfully, but these errors were encountered: