exec
Last updated
Last updated
A simple provider that allows running arbitrary scripts when initializing providers, and provides the exec action type.
Note: This provider is always loaded when running Garden. You only need to explicitly declare it in your provider configuration if you want to configure a script for it to run.
Below is the full schema reference for the provider configuration. For an introduction to configuring a Garden project with providers, please look at our .
The reference is divided into two sections. The contains the complete YAML schema, and the describes each schema key.
The values in the schema below are the default values.
providers[]
providers[].name
The name of the provider plugin to use.
providers[].dependencies[]
List other providers that should be resolved before this one.
Example: ["exec"]
providers[].environments[]
If specified, this provider will only be used in the listed environments. Note that an empty array effectively disables the provider. To use a provider in all environments, omit this field.
Example: ["dev","stage"]
providers[].initScript
An optional script to run in the project root when initializing providers. This is handy for running an arbitrary script when initializing. For example, another provider might declare a dependency on this provider, to ensure this script runs before resolving that provider.
The following keys are available via the ${providers.<provider-name>}
template string key for exec
providers.
${providers.<provider-name>.outputs.initScript.log}
The log output from the initScript specified in the provider configuration, if any.
Type | Default | Required |
---|
> name
Type | Required |
---|
> dependencies
Type | Default | Required |
---|
> environments
Type | Required |
---|
> initScript
Type | Required |
---|
Type | Default |
---|
|
| No |
| Yes |
|
| No |
| No |
| No |
|
|