Skip to content

Create mcp approval support configuration#1288

Open
blublinsky wants to merge 1 commit intoopenshift:mainfrom
blublinsky:approval-configuration
Open

Create mcp approval support configuration#1288
blublinsky wants to merge 1 commit intoopenshift:mainfrom
blublinsky:approval-configuration

Conversation

@blublinsky
Copy link
Contributor

Description

Type of change

  • Refactor
  • New feature
  • Bug fix
  • CVE fix
  • Optimization
  • Documentation Update
  • Configuration Update
  • Bump-up dependent library

Related Tickets & Documents

Checklist before requesting a review

  • I have performed a self-review of my code.
  • PR has passed all pre-merge test jobs.
  • If it is a core feature, I have added thorough tests.

Testing

  • Please provide detailed steps to perform tests related to this code change.
  • How were the fix/results from this change verified? Please provide relevant screenshots or results.

@openshift-ci openshift-ci bot requested review from bparees and raptorsun February 17, 2026 11:56
@openshift-ci
Copy link

openshift-ci bot commented Feb 17, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign bparees for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@blublinsky
Copy link
Contributor Author

/retest

// 'tool_annotations' - approval based on per-tool annotations
// +kubebuilder:default=never
// +operator-sdk:csv:customresourcedefinitions:type=spec,displayName="Approval Type"
ApprovalType ApprovalType `json:"approvalType,omitempty"`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What options do we want to present to the users in CR? Would just enabling/disabling be enough?

When enabled, only read-only tools will not raise for approval - every other tool will.

This ApprovalType also allows raising for read-only tools (via always).

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. You can skip this configuratio
  2. You can use never as approval type

Both will bypass approval logic

@blublinsky blublinsky force-pushed the approval-configuration branch from 40895da to 55a1e92 Compare February 17, 2026 19:13
@openshift-ci
Copy link

openshift-ci bot commented Feb 17, 2026

@blublinsky: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants