Report config values and missing config fields in workflow describe - #13
Merged
Merged
Conversation
`taskmaestro workflow describe --input` now reports, per task: - `config_values`: the raw values from input.yaml for the provided fields, before Pydantic validation, so opaque markers pass through unchanged. Dates/datetimes become ISO 8601 strings, paths strings, sets sorted lists and non-string mapping keys JSON key strings. Bytes, NaN/infinity and keys colliding after conversion are rejected. - `missing_config_fields`: declared config_fields the input does not set. An incomplete input (e.g. a template with runtime-picker fields) is now described instead of rejected; the remaining Job validation (map sources, root inputs) still runs. `validate` and `run` stay strict. Both are null without --input. Closes #12
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
taskmaestro workflow describe --inputnow reports, per task:config_values: the raw values from input.yaml for the provided fields, before Pydantic validation, so opaque markers pass through unchanged. Dates/datetimes become ISO 8601 strings, paths strings, sets sorted lists and non-string mapping keys JSON key strings. Bytes, NaN/infinity and keys colliding after conversion are rejected.missing_config_fields: declared config_fields the input does not set. An incomplete input (e.g. a template with runtime-picker fields) is now described instead of rejected; the remaining Job validation (map sources, root inputs) still runs.validateandrunstay strict.Both are null without --input.
Closes #12