feat: resolve latest module releases to exact export pins - #5
Merged
Merged
Conversation
This was referenced Sep 16, 2026
Merged
Merged
Merged
Merged
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.
Add
--module-version latest --scaffoldfor public Terraform Registry modules. Resolve each selected resource module independently and write exact versions into the generated root. Keep the tested default offline and advance it to module version 1.0.1. Reject unsupported sources; stop before writes when resolution fails.Validation:
DATATF_TELEMETRY=0 make checkandmake e2epass. Both export layouts and both ownership scopes also pass import-only and clean post-import plans against the final local candidate modules. Thelatestpath passes the same four checks with real public Registry lookups and the fake workspace. Module suites contain 100 passing Terraform tests; resource modules pass with providers 1.128.0 and 1.130.0. CI is green on all 12 PRs.All ten resource modules and the workspace pattern are published as 1.0.1. The workspace pattern pins each child at 1.0.1. DataTF 1.1.0 defaults to these tested versions. Both layouts and scopes pass import-only and clean post-import plans against the published modules, including real Registry lookups with
latest. Arbitrary future latest releases still require plan review.Related PRs:
Review: AutoReview ran with GPT-6 Astra (
xhigh) and Claude Fable 5.1 (high) through P2 across all 12 PRs. Confirmed findings are fixed and covered by regression tests: stable build-metadata versions, nullable provider defaults, and provider-supported service-credential bindings. The reported cluster-policy test failure does not reproduce with either supported provider version or in CI. No known actionable finding remains. Follow-up fixes pass tests and CI; this does not claim a second full review of every follow-up commit.