Repository navigation
infra: enforce Terraform root vs child module layout - #55
Merged
Merged
Conversation
This was referenced Sep 14, 2026
Remediate workers miniflare → sharp high-severity audit findings without force-upgrading blindly
#57
Open
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.
Standardizes the existing
.ores-infra.tomlconvention into an explicit Terraform root/child-module contract.modules/*is reusable, environment-agnostic child-module code with no backend/state ownership.environments/<env>/*is the root-module/state boundary and may mix module calls with true environment-only resources.This PR does not move existing Terraform resource addresses or state.