wendy cloud device rename
Rename a device in Wendy Cloud and set its mDNS hostname
Syntax
wendy cloud device rename [name] [flags]Examples
wendy cloud device rename --helpArguments
Argument notation from the CLI: [name]. Angle brackets mark required values; square brackets mark optional values. See Details for command-specific validation.
Flags
Flags below include inherited options. Types and defaults come from the CLI source. An empty default means no value is configured.
| Flag | Type | Default | Description |
|---|---|---|---|
--broker-url | string | (empty) | Tunnel broker host:port (default: cloud :443 endpoint, otherwise <cloud-host>:50052) |
--cloud-grpc | string | (empty) | Cloud gRPC endpoint to use (defaults to the device's enrolled cloud host) |
--device | string | (empty) | Target device hostname; wendy run accepts a comma-separated list to deploy one build to several devices (needs a remote build host and --detach). Defaults to $WENDY_DEVICE, then the saved default device |
--json | bool | false | Output in JSON format |
Output
Output depends on the operation and selected target. Use the command help for additional guidance..
JSON output
The global --json option requests machine-readable output. The CLI also selects JSON mode when no interactive terminal is attached. Support and payloads are command-specific; this flag does not guarantee a single JSON document for commands that stream logs or invoke build tools. Consult Details before parsing command output.
Exit codes
The CLI entry point returns 0 on success and for its user-cancelled or default-cleared results. Other returned errors exit with 1 and print a diagnostic to stderr. Some operations may terminate through subprocess or signal handling; do not infer application health from the CLI exit code alone.
Common errors
Check argument values and flag combinations against the synopsis above. For discovery, build, port, and readiness failures, see deployment troubleshooting. Command-specific constraints are in Details.
See also
Details
Renames a device in two places: its asset name in Wendy Cloud and its hostname (and mDNS '.local' name) on the device itself. A single name is applied to both. The hostname is set literally — no 'wendyos-' prefix is added — though the interactive prompt is prepopulated with 'wendyos-' as a starting point.
The name must be a valid DNS label: it starts with a lowercase letter, contains only lowercase letters, digits, and hyphens, does not end with a hyphen, and is at most 63 characters.
Use the command help for additional guidance.