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
Similar to #6035 but without the aspect of running the stages in parallel (which would be great but a separate issue), it would be great if one can run dvc repro foreach_stage_name which then get expanded to all the individual stages which DVC produces from the foreach stage. It can be annoying and cumbersome having to specify each foreach_stage_name@substage_name_or_id separately.
Given dvc.yaml:
stages:
foreach_stage_name:
foreach:
- a
- b
do:
...
it should be possible to run dvc repro foreach_stage_name. Currently, I have to run
Looking at the documentation of dvc repro, it appears this could be done using --glob:
dvc repro --glob "foreach_stage_name@*"
While this satisfies my use case, I still wonder if for foreach stages it would make sense to not have to use an explicit glob pattern? Given the special @ separator in the stage names and the stage key specified when editing the dvc.yaml. Intuitively, I thought this should work. When it didn't, I hadn't realized that the --glob option existed until now.
The text was updated successfully, but these errors were encountered:
@schuhschuh, this was introduced together with the same feature in 2.0. It might have been the case that the other stage did not need to be reproduced.
Similar to #6035 but without the aspect of running the stages in parallel (which would be great but a separate issue), it would be great if one can run
dvc repro foreach_stage_name
which then get expanded to all the individual stages which DVC produces from the foreach stage. It can be annoying and cumbersome having to specify eachforeach_stage_name@substage_name_or_id
separately.Given
dvc.yaml
:it should be possible to run
dvc repro foreach_stage_name
. Currently, I have to runLooking at the documentation of
dvc repro
, it appears this could be done using--glob
:While this satisfies my use case, I still wonder if for
foreach
stages it would make sense to not have to use an explicit glob pattern? Given the special@
separator in the stage names and the stage key specified when editing thedvc.yaml
. Intuitively, I thought this should work. When it didn't, I hadn't realized that the--glob
option existed until now.The text was updated successfully, but these errors were encountered: