docs: fold provider wrapper-scope + reachability-keyed-ack notes into roadmap#15
Merged
Merged
Conversation
… roadmap Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Follow-up to the standalone
POST /confirmroadmap entry, folding in two refinements that came back from the terraform-provider side after the design converged.Operator-scope corollary: the wrap token is necessarily broader than the apply it guards (wrapping a
network:routes-only apply needs:rwon all 7network-backed resources, since the package-wide revert can restore any of them). The guide must say "mint the wrap token at package granularity" or a narrow token hits a confusing 403 on arm.Reference wrapper: its natural home is the provider repo (the concrete consumer), and its ack-vs-rollback must key on management-path reachability, not
terraform apply's exit code. A partial failure where the box is still reachable should ack (Terraform already recorded the resources that succeeded, so acking keeps the box consistent with state); only an unreachable box should be left to auto-revert. This resolves the "forgotten ack silently reverts committed sibling changes" hazard cleanly.Docs-only. No wire surface changes.
🤖 Generated with Claude Code