Make remote state reference handling more robust #49
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 the event where a hook script execution is required in order to make terraform
execute in order to show the state (such as when a hook script defines the value of
specific variables) there is a circular condition where the remote outputs can not
be determined by terraform directly, and still made available to the hook.
In order to work around this issue, when the two initial mechanisms to get remote
state items fail, then the state is acquired from the backend (currently only S3
supported), and the state of the remote reference is used directly to obtain the
values.
This PR also updates dependencies to address GHSA-7m4m-pwhv-49c5