fix: Fix zone auto-detection when var.zones are not set #534
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In v17.0.0 (#507) there was an error in the detection of the default value for
local.zone
, which takes place whenvar.zone
is not set:This PR fixes this issue.
Solution details
In line 21 we see:
It means that we are going to rely on
data.google_compute_zones
only whenvar.zone == null
. So that, we should flip the "count" condition fordata.google_compute_zones
, as I did in this PR.After that fix
terraform plan
works as expected with both cases: whenvar.zone
is defined and when when it's not defined (null).cc @imrannayer , @g-awmalik