Debug Actions

Available as the agent.replicante.io/debug.* family of identifiers, these actions focus on debugging, testing and understanding an agent.

None of these action do much useful work but they can be used to:

• Test the node actions system and the agent.
• Understand how node actions work, execute and impact the agent.
• Provide a a way to write demos and examples that actually run without risk to the node.

Node actions can be scheduled directly through the specification API or through Replicante Core. As a reminder, the is the YAML to apply new node actions to Replicante Core:

apiVersion: replicante.io/v0
kind: NodeAction

metadata:
  # Can override the namespace with --namespace=test-namespace
  namespace: default
  # Can override the cluster with --cluster=test-cluster
  cluster: target-cluster-id
  # Can override the cluster with --node=test-node
  node: target-node-id

spec:
  action: agent.replicante.io/debug.${ACTION}
  args: null

Each debug action supports different args as detailed below.

Fail

This action handler always returns an error from its Action::invoke implementation. Mainly useful to test and explore how errors during action execution are handled.

Any args specified for the action are ignored.

Progress

This action will move from the NEW state to RUNNING on first invocation and then from RUNNING to DONE the invocation after.

Success

The action succeeds as soon as it is invoked and any args to it are ignored.