Agentic Data Plane
Preview

rpk ai trigger

Manage the triggers on an agent: the configured ways an agent is invoked from the outside (Microsoft Teams, or a cron schedule).

A trigger belongs to exactly one agent, and its resource name carries that parent: agents/{agent}/triggers/{trigger}. So create and list take the parent agent, while get, update, delete and runs take the full two-segment name they print.

The trigger id is server-assigned unless you pass --id. The kind (--teams-* or --cron-*) is fixed at creation; to change it, delete and recreate.

adp-api is a registry: it stores the trigger config but never validates the credentials or resolves the secret refs. A trigger that is accepted here can still be reported unhealthy by the component that operates it.

Usage

rpk ai trigger [flags]

Global flags

Value Type Description

--config

string

Redpanda or rpk config file; default search paths are ~/.config/rpk/rpk.yaml, $PWD/redpanda.yaml, and /etc/redpanda/redpanda.yaml.

-X, --config-opt

stringArray

Override rpk configuration settings; -X help for detail or -X list for terser detail.

--ignore-profile

bool

Ignore rpk.yaml and redpanda.yaml; use default settings.

--profile

string

rpk profile to use.

-v, --verbose

bool

Enable verbose logging.