Repository navigation
Keep capability status under assistant control - #114
Merged
Merged
Conversation
scotwells
marked this pull request as ready for review
October 2, 2026 15:03
JoseSzycho
approved these changes
Oct 2, 2026
This was referenced Oct 4, 2026
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
2 participants
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.
Keep capability acceptance and composition results under the assistant’s control. Register separate status permissions for CapabilityBindings without granting them to customers or capability publishers; ordinary binding reads still show conditions. Preserve the assistant’s existing Kubernetes RBAC status grant and correct comments that implied withholding base
patchalso preventedPUT /status.Depends on Milo #824 and provider #139. Enforcement remains off by default. Before enabling it globally, Conversation
/messagesand/sendmessageneed separate non-status adoption.Validation: Milo, dev-crd, and production Kustomize builds; schema validation; all 5 registrations and 6 IAM Roles inspected for direct/inherited status grants. Other assistant resources serve no
/statusendpoint.