Mach Composer¶

All MACH composer specific configurations options. These govern how theapplication as a whole will function, where variables can be sourced fromand which plugins are loaded, among others.

Example¶

mach_composer:version:1variables_file:variables.yml

Schema¶

Required¶

• version (Number) Schema version to be used for this configuration. Currently only version 1 is supported.

Optional¶

• variables_file (String) Define a variables file. Can be used instead of using the--var-file option. Seevariables for more information.
• plugins (List of Block) List of plugins to be used. Seeplugins for more information. By default, the amplience, aws, azure, commercetools, contentful and sentry plugins are loaded ( seebelow for nested schema)
• cloud (Block) Cloud specific configuration. Seecloud for more information. Seebelow for nested schema). If not set no cloud specific features will be used.
• deployment (Block) Deployment specific configuration. Seedeployment for more information. If not mach-composer will default to site-scoped deployments. Seebelow for nested schema).

Nested schema forplugins¶

Required¶

• source (String) The source of the plugin. This will be used to download the plugin from GitHub releases. The format isorganization/repository.

Optional¶

• version (String) The version of the plugin to be used. If not specified, the latest version will be used.

Nested schema forcloud¶

Required¶

• organization (String) The organization in mach-composer cloud this project belongs to.
• project (String) The project name in mach-composer cloud.

Nested schema fordeployment¶

Required¶

• type (String) The deployment type to be used. Currentlysite andsite-component are supported. These will override the global deployment settings for this site