terraform: output nodes can have depends_on
#10072
Merged
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.
This adds
depends_on
tooutput
.The primary use case for this is to depend on resources that may have a side effect that the output is depending on. For example: a resource may be a local-exec provisioner to create a file that the output is reading with
${file()}
.Another reason to add this is to support module-level
depends_on
which would impose adepends_on
on all contained items (resources, modules, etc.).This doesn't put a "Dependencies" list into the state for outputs because dependency ordering only matters for creation and updates, not for orphan destruction.