When you use terragrunt or even a terraform module calling terraform-aws-consul module you may have spot_price defined but you don't want to assign any value because you want the instances to be on-demand. However since it's templated with the use of a variable, spot_price is always present. Unfortunately the type=number for spot_price makes it impossible to assign an empty value because terraform/terragrunt will tell you that null or "" is not a number.
The change is a simple as not enforcing the type = number in variables.tf
Description
When you use terragrunt or even a terraform module calling terraform-aws-consul module you may have
spot_price
defined but you don't want to assign any value because you want the instances to be on-demand. However since it's templated with the use of a variable,spot_price
is always present. Unfortunately thetype=number
forspot_price
makes it impossible to assign an empty value because terraform/terragrunt will tell you thatnull
or""
is not a number.The change is a simple as not enforcing the
type = number
invariables.tf
Use case (simplified version)
terragrunt.hcl
terraform in-house module
Documentation
N/A
TODOs / Related issues
There isn't any issue number yet and I couldn't find one.