sincecutoff.com
/v1/json /v1/md llms.txt
← all changes

render commands accept RENDER_OUTPUT as a global output format

Introduced 2026-02-11 · score 0.98

HOW TO USE IT

When scripts or CI need a consistent Render CLI output format, set `RENDER_OUTPUT` to `json`, `yaml`, or `text`. Override it for a command with `--output` or `-o`; the CLI reference documents output selection and TTY behavior, but the current docs are newer than v2.9.0.

export RENDER_OUTPUT=json
render services list -o yaml
render services list -o text | grep my-service

WHY THIS HELPS

Set a consistent output format for Render CLI commands used in scripts or CI, with a per-command override where needed.

REQUIREMENTS AND LIMITATIONS

  • Version: v2.9.0
  • RENDER_OUTPUT: Sets the output format globally; documented precedence is command `--output`/`-o`, then this environment variable, then TTY/CI auto-detection. The CLI guide documents `json`, `yaml`, and `text` values.
  • --output / -o: Sets a command's output format. The current CLI reference lists `interactive`, `json`, `yaml`, and `text`; it says output auto-switches to text on non-TTY.
  • Prerequisite: Install the Render CLI; the guide describes installation methods and advises running `render` with no arguments to confirm installation.
  • Output selection precedence is command `--output` / `-o`, then `RENDER_OUTPUT`, then auto-detection based on TTY/CI signals.
  • Docs conflict: The currently published CLI docs identify v2.28.0/v2.29.0, later than the card’s v2.9.0; no differing `RENDER_OUTPUT` behavior was found. Current reference lists `interactive` as a supported `--output` value, while the guide names `json`, `yaml`, and `text` for non-interactive use.

FIRST-PARTY EVIDENCE

Check the installed version and the source before using it. Entry JSON

Report a problem with this card