Repository navigation
fix(stack): forward every selected namespace from every compartment - #5
Merged
Merged
Conversation
arsenstorm
marked this pull request as ready for review
November 12, 2026 22:21
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.
Broken: services first used after Apply weren't forwarded until the next Apply. Root plus one subcompartment could need 3 Connector Hubs, over the free tier's 2.
Cause: Apply kept only the namespaces each compartment had data for, and grouped compartments by that count.
Fix: every compartment gets every selected namespace. A Connector Hub covers 2 compartments with the 25 default namespaces, 5 with 10 or fewer. Plan stops before any change when the region's Connector Hub limit is too low. The user who runs Apply now also needs
inspect limits in tenancy.terraform testchecks the counts and the limit in CI.