Repository navigation
Conversation
Signed-off-by: Haytham Abuelfutuh <haytham@union.ai>
Signed-off-by: Haytham Abuelfutuh <haytham@union.ai>
Signed-off-by: Haytham Abuelfutuh <haytham@union.ai>
Signed-off-by: Haytham Abuelfutuh <haytham@union.ai>
Signed-off-by: Haytham Abuelfutuh <haytham@union.ai>
Signed-off-by: Haytham Abuelfutuh <haytham@union.ai>
This branch has not been deployed
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.
Persist server-selected secure namespace placement in run and app specs.
Run and app services can resolve a secure namespace once at creation time and carry that immutable assignment through retries, recovery, updates, and operator reconciliation. Empty fields preserve legacy namespace behavior, and clients cannot change the server-owned assignment on update.
Validation: regenerated Go and schema artifacts with buf.