Magnolia 5.7 reached extended end of life on May 31, 2022. Support for this branch is limited, see End-of-life policy. Please note that to cover the extra maintenance effort, this EEoL period is a paid extension in the life of the branch. Customers who opt for the extended maintenance will need a new license key to run future versions of Magnolia 5.7. If you have any questions or to subscribe to the extended maintenance, please get in touch with your local contact at Magnolia.
Definition items such as template definitions, dialog definitions and similar types (see list below), which are defined on the JCR configuration workspace, can be exported as YAML file to be used as item definition file within a light module. Creation of these files is useful for instance, when you want to migrate JCR based definition items into files.
The action to download is named Download definition.
If you want to export JCR data in YAML format in order to import it in JCR again later, use the Export action instead.
List of definition items which can be downloaded as YAML
The Download definition action is available for all definition items that can be configured in YAML and that have their own registry:
- App definitions
- Dialog definitions
- Field type definitions
- Media editor definitions
- Message view definitions
- Renderer definitions
- REST endpoint definitions
- Template definitions
- Theme definitions
- Virtual URI mappings
- Workflow definitions
- Work item handler definitions
When using YAML files originating from a Download definition action, you must change the file name if you want to use it within a module. For instance, the name of the YAML file defining an app must reflect the app name with the pattern <app-name>.yaml.
Overview
Content Tools