I am attempting to deploy the vpc with the the database_subnets from #36. I am getting a failure due to lack of deployment in multiple availability zones. I am not sure how I can fix this as it seems to only deploy region specifically.
As it was just recently merge I am curious how this is intended to be handled. As I can't deploy a single subnet let alone across regions.
I would need some other subnet to be provisioned to another az. Perhaps I'm missing some obvious config value. So I'm trying to figure out how to handle it. Perhaps utilizing the experimetal tf_aws_availability_zones
I can provide a working mini-example. But if you plug in any static provider configs with database_subnets it appears to fail.
Closing due to my own stupidity of trying to deploy across regions as opposed to availability zones within the same region. I cross-region, and single az-but failed to use multi-az in testing.
Summary
Deploying a vpc with
database_subnets
failsDetails
I am attempting to deploy the vpc with the the database_subnets from #36. I am getting a failure due to lack of deployment in multiple availability zones. I am not sure how I can fix this as it seems to only deploy region specifically.
As it was just recently merge I am curious how this is intended to be handled. As I can't deploy a single subnet let alone across regions.
I would need some other subnet to be provisioned to another az. Perhaps I'm missing some obvious config value. So I'm trying to figure out how to handle it. Perhaps utilizing the experimetal tf_aws_availability_zones
I can provide a working mini-example. But if you plug in any static provider configs with database_subnets it appears to fail.