Conversation
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
This PR adds declaration-only provider-gap support for fork-PR contributor approval. Repository declarations are normalized and validated in
terraform/locals.tf; the planned desired-state projection is emitted without adding a Terraform resource for the provider gap. A GET-only verifier classifies the projected organization and repository targets, and the reusable workflow folds those results into the existing sanitized drift summary, issue lifecycle, and explicit final gate.The merged F3 inline summary and reporter projection code was deleted from the workflow and reimplemented as the
summaryandreportsubcommands oftools/verify_provider_gaps.py. This keeps the two public projections on one closed result validator and one private-resource redaction boundary.At reviewed head
4e762f7f8a2666817233a893dcda2260ac00a5e4, the reusable-workflow numstat against F3 base73b86e869fe4e1c61dd1e83ebc52d6adbc50f33fwas explicitly +45/-365. At final head73b96de9d1656097c5ee7a5f7be869355c6b58b6, it is +54/-367.Structural move and semantic deltas
The renderer move intentionally changes these operational boundaries:
trueorfalse;plan.json, and the desired-state projection, and requires the plan members needed to build the redaction union;Terraform applystep because apply is not analways()step;always() && detectorpredicate so it can report verifier or summary failures while the final gate independently requires explicit verifier status zero.v7 fix delta
SIGALRMdeadline around connect, send, header parsing, and complete body reading while retaining socket timeouts and no retry. Trickle-header and trickle-body peers are bounded, and the prior handler is restored.Terraform applyandGuard repository destroysby name, and the organization plan-only fixture again coversplan_only=truewith detector mode false.drift_issueinput now describes the Terraform, inventory, and provider-gap union.Captured acceptance evidence
Head, parent, commit count, clean worktree, and workflow numstats:
Local acceptance at the pinned toolchain:
Each prescribed mutation was applied alone in a scratch copy;
mutant=1is red andreverted=0is green:No new repository path was added; the modified tracked paths remain outside the deny-all ignore, no tracked file is ignored, and the committed diff is clean:
Hosted checks at the final head all completed successfully except the configured OpenSSF skip:
The hosted
Terraform Framework Tests / Validate & Testlog shows the final counts and the new regression cases executing: