Skip to main content
Version: Next (Private Preview)

nexoctl command reference

This reference distinguishes an implemented command from an operationally supported workflow.

Command list

CommandDescriptionSupport status
loginAuthenticate and save Control Plane credentials.Unavailable: interactive token fields do not match the API; --api-key exposes the key in argv.
statusList projects or request detailed environment status.Unavailable end to end: no supported CLI authentication path; detailed fields also differ.
upgradeCheck versions or request a rollout.Unavailable: CLI request/status contracts do not match the current Control Plane.
diagnostics, diagCollect Kubernetes status, logs, events, optional metrics, and a JSON summary.Supported with appropriate cluster access.
support-bundle, supportbundle, supportGenerate, inspect, or redact a support archive.Collection supported; redaction is best-effort and inspection lists metadata/files only.
scaffoldGenerate a pipeline-plugin project.Available. Generated WASM workflow is not complete; Go is the documented path.
validateValidate plugin manifest, SDK dependency, and build.Available.
testValidate/rebuild a plugin and attempt a smoke test at localhost:27017.Available; a skipped smoke test is not success evidence.
publishPackage and upload a plugin.Dry-run only recommended. API key is exposed in argv and archive contents are not allowlisted.
version, helpPrint version or help.Supported.

login

nexoctl login
nexoctl login --server https://api.nexo.io

Flags:

FlagDescription
--serverControl Plane base URL.
--api-keyAPI key login. Avoid: the key is visible in the process argument list and may be captured by monitoring/audit systems.

The interactive login response model expects snake-case token fields while the current Control Plane returns camel-case fields, so it does not persist a usable access token. Configuration would be stored in ~/.nexoctl/config.json with mode 0600, but that file permission does not correct the response mismatch or argv exposure.

status

nexoctl status
nexoctl status --wide

Flags: --project, --wide.

Do not use this as a supported Control Plane workflow until authentication and response models are aligned. There is no project switch command.

upgrade

Flags: --project, --env, --proxy-version, --manager-version, --check, --wait, and --timeout.

:::warning Not an operational upgrade path

The 0.2.0 CLI sends component-oriented fields while the current Control Plane requires a target environment and one bundle version. It also waits for status values that do not match the Manager acknowledgement lifecycle. Use the supported console or support-directed bundle workflow instead.

:::

diagnostics

Flags:

FlagDefaultDescription
--namespacenexoNamespace to inspect. Pass nexo-system for the standard Edge installation.
--outputstdoutJSON output path.
--log-lines200Lines collected per pod.
--include-logstrueInclude pod logs.
--include-metricsfalseAttempt metrics collection.
--widefalseEnable logs and metrics and collect 500 log lines.
nexoctl diagnostics \
--namespace nexo-system \
--output ./nexo-diagnostics.json

support-bundle generate

FlagDefaultDescription
--namespacenexo-systemTarget namespace.
--timerange1hRelative collection window.
--include-logstrueInclude pod logs.
--include-metricstrueInclude metrics snapshots.
--include-configtrueInclude Nexo resources and selected configuration.
--include-healthtrueInclude health endpoint snapshots.
--include-decisionstrueInclude decision snapshots when available.
--include-eventstrueInclude Kubernetes events.
--redact-secretstrueApply built-in best-effort redaction.
--outputrequiredOutput archive path.
--api-endpointemptyOptional Control Plane support-bundle endpoint.
--offlinefalseSkip API generation and collect through kubeconfig.
nexoctl support-bundle generate \
--namespace nexo-system \
--redact-secrets=true \
--output ./nexo-support.tar.gz

support-bundle inspect and redact

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

inspect prints the manifest and filenames; it does not scan file content for secrets. redact recognizes common key names, MongoDB URIs, bearer tokens, and selected key/value patterns. It can miss unlabelled tokens, other authorization schemes, account keys, private keys, and application-specific secrets.

Plugin commands

CommandFlags
scaffold--name (required), `--type=request
validate--dir
test--plugin-path (required), --config, --verbose
publish--api-key, --endpoint, --dir, --dry-run

publish recursively packages every file under --dir, excluding hidden directories but not hidden files. Until an allowlist/ignore mechanism and safe API-key input are implemented, use only --dry-run from a clean staging directory and inspect the archive before any separately approved upload.

Search Nexo documentation

Type to search titles, headings, and page content.