because we cant read in the availability zone from the state files we try to solve subnet -> region which leads to
{"level":"error","ts":1709827856.219598,"logger":"engine","msg":"Engine returned error: failed to evaluate group 4: failed to evaluate aws:availability_zone:region:stackpacks-private-subnet-1-region#Index: could not get default value for aws:availability_zone:region:stackpacks-private-subnet-1-region#Index: strconv.Atoi: parsing \"stackpacks-private-subnet-1-region\": invalid syntax"}
there are 3 major issues here
The properties we label as being of type 'Resource' dont map to iac
the AZ template requires specific naming to be accurate
we have to explicitly add the subnet -> region edge because imports cant create resources and the way region gets created is subnet -> az -> region leading us to path expand
For now we have allowed adding explicit edges if both are imported for contextual purposes
because we cant read in the availability zone from the state files we try to solve subnet -> region which leads to
there are 3 major issues here
For now we have allowed adding explicit edges if both are imported for contextual purposes