Advanced Configuration¶
This section has been placed in the Developer Guide because it details advanced configuration that should only be used by those with intimate knowledge of how Runway works.
Environment Variables¶
Environment variables can be used to alter the functionality of Runway.
- CI (Any)
If not
undefined
, Runway will operate in non-iterative mode.- DEBUG (int)
Used to select the debug logs to display
0
or not defined with show no debug logs1
will show Runway’s debug logs2
will show Runway’s debug logs and some dependency debug logs (e.g. botocore)
- DEPLOY_ENVIRONMENT (str)
Explicitly define the deploy environment.
- CFNGIN_STACK_POLL_TIME (int)
Number of seconds between CloudFormation API calls. Adjusting this will impact API throttling. (default:
30
)- RUNWAY_COLORIZE (str)
Explicitly enable/disable colorized output for CDK, Serverless, and Terraform modules. Having this set to a truthy value will prevent
-no-color
/--no-color
from being added to any commands even if stdout is not a TTY. Having this set to a falsy value will include-no-color
/--no-color
in commands even if stdout is a TTY. If the IaC tool has other mechanisms for disabling color output, using a truthy value will not circumvent them.Truthy values are
y
,yes
,t
,true
,on
and1
. Falsy values aren
,no
,f
,false
,off
and0
. RaisesValueError
if anything else is used.- RUNWAY_MAX_CONCURRENT_MODULES (int)
Max number of modules that can be deployed to concurrently. (default:
min(61, os.cpu_count())
)On Windows, this must be equal to or lower than
61
.IMPORTANT: When using
parallel_regions
andchild_modules
together, please consider the nature of their relationship when manually setting this value. (parallel_regions * child_modules
)- RUNWAY_MAX_CONCURRENT_REGIONS (int)
Max number of regions that can be deployed to concurrently. (default:
min(61, os.cpu_count())
)On Windows, this must be equal to or lower than
61
.IMPORTANT: When using
parallel_regions
andchild_modules
together, please consider the nature of their relationship when manually setting this value. (parallel_regions * child_modules
)- RUNWAY_LOG_FIELD_STYLES (str)
Can be provided to customize the styling (color, bold, etc) used for LogRecord attributes (except for message). By default, Runway does not apply style to fields. For information on how to format the value, see the documentation provided by coloredlogs.
- RUNWAY_LOG_FORMAT (str)
Can be provided to use a custom log message format. The value should be a format string using %-formatting. In addition to being able to use LogRecord attributes in the string, Runway provides the additional fields of
%(hostname)s
and%(programname)s
.If not provided,
[%(programname)s] %(message)s
is used unless using debug, verbose or no color. In that case,%(levelname)s:%(name)s:%(message)s
is used.- RUNWAY_LOG_LEVEL_STYLES (str)
Can be provided to customize the styling (color, bold, etc) used for log messages sent to each log level. If provided, the parsed value will be merged with Runway’s default styling. For information on how to format the value, see the documentation provided by coloredlogs.
- RUNWAY_NO_COLOR (Any)
Disable Runway’s colorized logs. Providing this will also change the log format to
%(levelname)s:%(name)s:%(message)s
.- VERBOSE (Any)
If not
undefined
, Runway will display verbose logs and change the logging format to%(levelname)s:%(name)s:%(message)s
.