set TF_IN_AUTOMATION env var for terraform commands

[mcalhoun]

what

Set the TF_IN_AUTOMATION env var

why

If set, Terraform adjusts its output to avoid suggesting specific commands to run next. This can make the output more consistent and less confusing in workflows where users don't directly execute Terraform commands, like in CI systems or other wrapping applications such as atmos.

references

https://developer.hashicorp.com/terraform/cli/config/environment-variables#tf_in_automation

[osterman]

We deliberately didn't do this because it drops all color formatting. IMO the CI flags are a bit dated because all modern CI systems work with full terminal support (e.g. ansi color)

[osterman]

If we do this, we should do it only when output is not needed by the end user.

[mcalhoun]

@osterman I think you have misunderstood this flag, the color formatting still happens, it just drops the verbose instructions.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

In both cases below, color output is displayed, the only difference is the verbose instructions, which the docs also indicate:

If TF_IN_AUTOMATION is set to any non-empty value, Terraform adjusts its output to avoid suggesting specific commands to run next. This can make the output more consistent and less confusing in workflows where users don't directly execute Terraform commands, like in CI systems or other wrapping applications.

$ TF_IN_AUTOMATION=true atmos terraform plan terraform-no-error -s test-test-test

Initializing the backend...

Initializing provider plugins...

Terraform has been successfully initialized!

Changes to Outputs:

• test = "Hello, World"

You can apply this plan to save these new output values to the Terraform state, without changing any real infrastructure.

$ atmos terraform plan terraform-no-error -s test-test-test

Initializing the backend...

Initializing provider plugins...

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

Changes to Outputs:

• test = "Hello, World"

You can apply this plan to save these new output values to the Terraform state, without changing any real infrastructure.