millions-plumber-38090
03/21/2023, 10:04 AMUsing eastus for resource module.network.azurerm_virtual_network_peering.vnet_hub_adm as its 'location' property could not be found.
as infracost is not picking up the regionbusy-agent-35515
03/21/2023, 10:14 AMINFRACOST_AZURE_OVERRIDE_REGION
to override the region, however it will be applied to all resources, not just one. https://www.infracost.io/docs/features/environment_variables/#environment-variables-to-override-cloud-provider-regionmillions-plumber-38090
03/21/2023, 10:15 AMbusy-agent-35515
03/21/2023, 10:16 AMenv
millions-plumber-38090
03/21/2023, 10:18 AM- path: env
include_all_paths: true
name: POD - CASH - SG
env:
INFRACOST_AZURE_OVERRIDE_REGION: southeastasia
terraform_vars:
environment: cash
geo: sg
purpose: devqa
- path: env
include_all_paths: true
name: POD - DELP - US
env:
INFRACOST_AZURE_OVERRIDE_REGION: centralus
terraform_vars:
environment: delp
geo: us
purpose: devqa
busy-agent-35515
03/21/2023, 10:19 AMINFRACOST_
env vars are globalvirtual_network_name
defined on the resource?millions-plumber-38090
03/21/2023, 10:22 AMlocals {
settings = local.regions[var.geo]
regions = {
## AE
## -----------------------------
"ae" = {
primary_region = {
name = "ae1"
location = "uaenorth"
}
secondary_region = {
name = "ae2"
location = "uaecentral"
}
and then passing that into the various modules
region = local.settings.primary_region.name
busy-agent-35515
03/21/2023, 10:25 AMwhite-airport-8778
03/21/2023, 2:59 PMAWS_REGION
env variable that is also read by Terraform, right?
AWS users can set AWS_REGION on a per-project basis in their Infracost config file, and since our CLI passes those env vars to the parser, that works ok for them.