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.
what
enabled
in all moduleswhy
enabled
flag to enable/disable all sub-modulesremote-state
throws errors whenenabled=false
and it tries to load YAML config filesinventory of problems (internal notes)
in 0.10.0, if you set
enabled=false
, then the backend module will not get the environment or stage, so it won't find the right stack and will error that i cannot find the stack. So in 0.11.0 we now setcount=0
whenenabled=false
on data resources. This would happen during aterraform apply
whenenabled=false
for some module that depended onremote-state
and/orbackend
, becausecount
was not respected.0.11.0 we have counts on the data sources, but this is now causing the "count of cannot be computed" type of problems anywhere we use the output of the remote state as an input put to another module that performs a count on that input (nested counts). Historically, counts on data sources has been problematic.
components need to work with remote state all returning null (which most of them don't), or disabling them does not remove the requirement that the remote state exists.