QuiltExceptionis caused by
is_message_required: true. Here's how we can pass the workflow:
metadata_schema: superheroes. Therefore, the
test/packagemetadata must validate against the JSON Schema at
superherois a required property:
metadata_schemaare set, so both
messageand package metadata are validated:
is_workflow_required: falsein your
config.yml, and specify
workflow=Nonein the API:
default_workflowcan be set in the config to specify which workflow will be used if
workflowparameter is not provided.
dateformatin your schemas. For example:
You must include the following schema version at the root of your config.yml in order for any catalog-specific features to function:
package_handlekey in one or both of the following places:
catalog.package_handle.(files|packages)at the root of config.yml to affect all workflows
workflows.WORKFLOW.catalog.package_handle.(files|packages)to affect the tabs and workflow in question
By default, patterns are not anchored. You can explicitly add start (
^) and end (
$) markers as needed.
WORkFLOW.entries_schema. The provided schema runs against an array of objects known as package entries. Each package entry defines a logical key (its releative path and name in the parent package) and size (in bytes).
browseany package and then
pushit to any bucket that you choose.
successorsproperty to the config. A successor is a destination bucket.
true(the default), all package entries will be copied to the destination bucket. If
false, all entries will remain in their current locations.