When using yaml to json conversion as it happens when using Terraform’s helm provider with a helm chart’s values.yaml file, it won’t be possible to check and get any useful validation errors, even when your terraform plan is run.
In order to check before running your plan or if you have any errors you can use yq passing as below using the values.yaml file
yq -p yaml -o json values.yamlYou are trying to run locally the terraform plan, while using the Terraform’s Cloud remote backend, before commiting your changes to your repo and running it through Terraform’s Cloud UI, and you are getting the previous error message:
Error: Invalid provider configuration
Remember to add the environment variables needed for your provider (AWS, Google, Exoscale etc) in the Variables section of your Terraform Cloud setup.
Even you have added them before, using a new Workspace means you will need to add them to each new workspace.
If you would like to get more detailed overview when using terraform plan, you can turn trace logging on by setting setting the environment variable TF_LOG to a non-zero value, e.g. export TF_LOG=1 or TF_LOG=1 terraform plan
Using the asdf version manager to manage versions of various binaries like terraform, vault or packer is easily done by following the instructions below:
asdf plugin add terraform asdf install terraform latest asdf global terraform 0.14.9 asdf list terraform 0.14.9 terraform --version Terraform v0.14.9
You would like to output some additional information (ie port number) in addition to the variable provided by Terraform.
Use interpolation of the Terraform variable using ${var} together with the rest of the string you would like to output, like:
output "kibana_endpoint" {
value = "http://${aws_instance.elasticsearch.public_ip}:5601"
description = "The Kibana endpoint"
}More information about the language https://learn.hashicorp.com/tutorials/terraform/outputs?in=terraform/configuration-language