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.
Subcommands
| Command | Description |
|---|---|
Reconcile triggers from one or more YAML manifests. For each manifest: create the resource if absent, otherwise update every field that differs from the live resource. |
|
Create a trigger on <agent>, given as the agent id ( |
|
Delete one trigger. <name> is the full resource name, for example, agents/my-agent/triggers/t1a2b3c4. |
|
Dry-run of apply for triggers. Prints, per manifest, whether apply would create, update (and which fields), or leave the resource unchanged. |
|
Get one trigger. <name> is the full resource name, for example, agents/my-agent/triggers/t1a2b3c4. |
|
List every trigger on <agent>, given as the agent id ( |
|
List the recorded fires of a cron trigger, newest first. <name> is the full trigger resource name, for example, agents/my-agent/triggers/t1a2b3c4. |
|
Update one trigger. <name> is the full resource name, for example, agents/my-agent/triggers/t1a2b3c4. |
Global flags
| Value | Type | Description |
|---|---|---|
|
string |
Redpanda or |
|
stringArray |
Override |
|
bool |
Ignore |
|
string |
|
|
bool |
Enable verbose logging. |