Repository navigation
deterministic and unique namespace fallback for unconfigured policy files - #3
Merged
Merged
Conversation
…licy files Signed-off-by: Yossi Elias <yelias@redhat.com>
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
opg-{repo}-{user}) whenopenshift-policy.yamlhas no namespaces configured, giving new users a working setup without manual policy editingderive_default_ns()to the hook with full sanitization (lowercase, special char replacement, length caps) to stay within Kubernetes' 63-char namespace limitopenshift-policy.example.yamlso users can see the permission model without touching the live policyopenshift-policy.yamlof sample namespaces so the default derivation activates out of the boxSecurity note
The README explains why the agent must never read or edit the policy file directly. The derivation logic resides within the hook (which the agent cannot modify), and a copy of this function is embedded in the target skill prompts so that both sides deterministically compute the namespace—preserving the security boundary between the agent and its constraints.