Skip to content

docs(workspace-config): document executionOrder shape validation and … - #103

Open
finalerock44 wants to merge 1 commit into
mainfrom
fix/dcd-cli-110-execution-order-docs
Open

docs(workspace-config): document executionOrder shape validation and …#103
finalerock44 wants to merge 1 commit into
mainfrom
fix/dcd-cli-110-execution-order-docs

Conversation

@finalerock44

@finalerock44 finalerock44 commented Aug 13, 2026

Copy link
Copy Markdown
Contributor

…fix continueOnFailure default

Two corrections to the executionOrder section, prompted by dcd-cli#110:

  • continueOnFailure was documented as defaulting to false. The CLI has always defaulted it to true (three read sites agree, and it is now the schema default). Corrected, with a note on when to set it to false.
  • Added a warning block for the shape mistake the issue reported: a bare list of flow names under executionOrder. It is not valid Maestro, older CLI versions silently ignored it and ran every flow in parallel while still reporting success, and the CLI now rejects it outright. Shows the wrong and right forms side by side so it is findable by anyone hitting the error.

Also noted that unrecognised top-level keys are now warned about, which is what catches flowOrder, a top-level continueOnFailure, and tags: in place of includeTags/excludeTags.


View with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is enabled.

…fix continueOnFailure default

Two corrections to the executionOrder section, prompted by dcd-cli#110:

- continueOnFailure was documented as defaulting to false. The CLI has always
  defaulted it to true (three read sites agree, and it is now the schema
  default). Corrected, with a note on when to set it to false.
- Added a warning block for the shape mistake the issue reported: a bare list
  of flow names under executionOrder. It is not valid Maestro, older CLI
  versions silently ignored it and ran every flow in parallel while still
  reporting success, and the CLI now rejects it outright. Shows the wrong and
  right forms side by side so it is findable by anyone hitting the error.

Also noted that unrecognised top-level keys are now warned about, which is
what catches flowOrder, a top-level continueOnFailure, and tags: in place of
includeTags/excludeTags.
@finalerock44 finalerock44 self-assigned this Aug 13, 2026
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

Successfully merging this pull request may close these issues.

1 participant