cloud: terraform output should gracefully handle 503 errors
#35143
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jbardin
approved these changes
May 10, 2024
brandonc
force-pushed
the
TF-15181-terraform-output-should-gracefully-handle-503-errors
branch
from
932f5e8
to
0efd586
Compare
brandonc
deleted the
TF-15181-terraform-output-should-gracefully-handle-503-errors
branch
|
Reminder for the merging maintainer: if this is a user-visible change, please update the changelog on the appropriate release branch. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #35105
When outputs are not available while using cloud backend, terraform will now silently retry while logging attempts. If retries are canceled or time out after one minute, an error is displayed (See below for screenshots)
Target Release
1.9.x
Draft CHANGELOG entry
ENHANCEMENTS
terraform outputwith cloud block: terraform no longer suggests that data loss could occur when outputs are not availableScreenshots
Before:
After (With TF_LOG, canceled):
After (With TF_LOG, deadline exceeded):
Please note the actual message says "within the deadline" not actually "within the timeout"