Using TF_WORKSPACE allow and override workspace selection. TF_WORKSPACEįor multi-environment deployment, in order to select a workspace, instead of doing terraform workspace select your_workspace, it is possible to use this environment variable. Terraform may be unable to find providers, modules, and other artifacts. To the next, so it's important to have this variable set consistently throughoutĪll of the Terraform workflow commands (starting with terraform init) or else The data directory is used to retain data that must persist from one command In most cases it should not be necessary to set this variable, but it mayīe useful to do so if e.g. terraform subdirectory of theĬurrent directory, but the path given in TF_DATA_DIR will be used instead Per-working-directory data, such as the current backend configuration.īy default this data is written into a. TF_DATA_DIR changes the location where Terraform keeps its The value of the flag is parsed as if you typed it directly to the shell.ĭouble and single quotes are allowed to capture strings and arguments willīe separated by spaces otherwise. You can set TF_CLI_ARGS_plan="-refresh=false". As an example, to specify that only plans never refresh, Named command in the form of TF_CLI_ARGS_name then it will only affect The flag TF_CLI_ARGS affects all Terraform commands. Is the equivalent to manually typing: terraform apply -input=false -force. This behavior ensures that flags on the command-line take precedence overįor example, the following command: TF_CLI_ARGS="-input=false" terraform apply -force (such as plan) and before any flags specified directly on the command-line. These arguments are inserted directly after the subcommand Modifying default behavior of Terraform on your own system. This allows easier automation in CI environments as well as The value of TF_CLI_ARGS will specify additional arguments to theĬommand-line.
For more on how to use TF_VAR_name in context, check out the section on Variable Configuration.
0 kommentar(er)
