Repository navigation
Record the real OpenTofu checks and the external method's stability - #18
Merged
Merged
Conversation
6 tasks done
Ilyes512
force-pushed
the
docs/GH-5-verify-real-opentofu
branch
from
October 12, 2026 21:20
81c3362 to
ed0748b
Compare
This file contains hidden or 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
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.
Summary
encrypted_data; the break-glass command decrypted a real state object from the S3 backend in specsnl/specsops-opentofu#14 (PR specsnl/specsops-opentofu#24)decryption failed for all provided methods, with the cause in tofu-age's stderr — and, with locking on, as a misleadingError acquiring the state lockerrorghcr.io/specsnl/opentofu:0.2.0: envelopes for state and saved plans, a clean second plan, a wrong or missing identity fails, a saved plan appliesCloses #5