SecondaryFileSchema

Secondary files are specified using the following micro-DSL for secondary files:

* If the value is a string, it is transformed to an object with two fields pattern and required * By default, the value of required is null (this indicates default behavior, which may be based on the context) * If the value ends with a question mark ? the question mark is stripped off and the value of the field required is set to False * The remaining value is assigned to the field pattern

For implementation details and examples, please see this section

in the Schema Salad specification.

Members

Mixins

__anonymous
mixin genBody
Undocumented in source.

Variables

pattern_
Union!(string, Expression) pattern_;

Provides a pattern or expression specifying files or directories that should be included alongside the primary file.

required_
Union!(None, bool, Expression) required_;

An implementation must not fail workflow execution if required is set to false and the expected secondary file does not exist. Default value for required field is true for secondary files on input and false for secondary files on output.

Mixed In Members

From mixin genBody

__anonymous
mixin genBody_!saladVersion
Undocumented in source.

Meta