Variables can be used to defined inputs and outputs for the build and deployment stages. They can also be used to make Errands configurable.
Variables are strongly typed, which is checked at both build and deploy time. A task can’t succeed if the required variables have not been configured correctly.
|id||A unique name for this variable. Required field.|
|type||The variable type. Before executing any steps Escape will make sure that all the values match the types that are set on the variables.|
|One of: |
|default||A default value for this variable. This value will be used if no value has been specified by the user.|
|description||A description of the variable.|
|friendly||A friendly name for this variable for presentational purposes only.|
|visible||Control whether or not this variable should be visible when deploying interactively. In other words: should the user be asked to input this value? It only really makes sense to set this to |
|options||Options that put more constraints on the type.|
|sensitive||Is this sensitive data?|
|items||If set, this should contain all the valid values for this variable.|
|eval_before_dependencies||Should the variables be evaluated before the dependencies are deployed?|
|scopes||A list of scopes (|