nexoctl how-tos

Access Control Plane workflows

Do not use nexoctl login, status, or upgrade as 0.2.0 operational workflows. Authentication and response contracts do not match the current Control Plane, and API key mode exposes the key in process arguments. Use the console workflow.

Collect diagnostics

nexoctl diagnostics \
  --namespace nexo-system \
  --output ./nexo-diagnostics.json

Treat output as sensitive operational data.

Generate and review a support bundle

nexoctl support-bundle generate \
  --namespace nexo-system \
  --redact-secrets=true \
  --output ./nexo-support.tar.gz
nexoctl support-bundle inspect ./nexo-support.tar.gz

Redaction is best-effort and inspection does not scan file contents. Extract into a restricted location and use your approved secret/DLP scanner plus manual review before transfer. If uncertain, do not send the archive.

nexoctl support-bundle redact \
  --output ./nexo-support-redacted.tar.gz \
  ./nexo-support.tar.gz

Develop and package a plugin

nexoctl scaffold --name example-step --type request --lang go
cd example-step
go mod tidy
make build
nexoctl validate
nexoctl test --plugin-path ./example-step.so

Use publish --dry-run only from a clean staging directory. The archive includes hidden files and has no allowlist; inspect extracted content before any separately approved upload.