Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
checkout
1commit
2dag
fetch
1freeze
/unfreeze
4pull
1push
1remove
3status
exp run
(already supported)repro
(already supported)stage list
(already supported)Closes #7323.
Notes:
checkout
might fail if any of the hash_info from the foreach group is missing (it'll still checkout). Same withpull
/push
/fetch
.commit
might fail if the workspace has any output missing from the foreach group (this is a bit annoying).remove
is not supported as it needs to modify templateddvc.yaml
file, which we don't support yet. We can skip it for now. Internally in dvc, we don't have a "foreach group" to remove, it's compiled away, so we only know about individual stages that it generates. So removing a definition for that foreach group requires custom logic to handle foreach group, and then need to imitate whatever behaviour we have forremove
, i.e unprotect from cache, remove fromdvc.lock
anddvc.yaml
, remove.gitignore
entries, etc.freeze
/unfreeze
is similar to 3. We don't modify parameterized stages and would require custom handling for that. We try not to modify dvc.yaml as much as possible.Related: #7462, #7385