Pp Render

<!-- GENERATED FILE — DO NOT EDIT.
     This file is a verbatim mirror of library/cloud/render/SKILL.md,
     regenerated post-merge by tools/generate-skills/. Hand-edits here are
     silently overwritten on the next regen. Edit the library/ source instead.
     See the repository agent guide, section "Generated artifacts: registry.json, cli-skills/". -->

Render — Printing Press CLI

Prerequisites: Install the CLI

This skill drives the render-pp-cli binary. You must verify the CLI is installed before invoking any command from this skill. If it is missing, install it first:

1. Install via the Printing Press installer. It defaults binaries to $HOME/.local/bin on macOS/Linux and %LOCALAPPDATA%\Programs\PrintingPress\bin on Windows:

   npx -y @mvanhorn/printing-press-library install render --cli-only

2. Verify: render-pp-cli --version
3. Ensure the reported install directory is on $PATH for the agent/runtime that will invoke this skill.

If the npx install fails (no Node, offline, etc.), fall back to a direct Go install (requires Go 1.26.6 or newer):

go install github.com/mvanhorn/printing-press-library/library/cloud/render/cmd/render-pp-cli@latest

If --version reports "command not found" after install, the runtime cannot see the binary directory on $PATH. Do not proceed with skill commands until verification succeeds.

When to Use This CLI

Use render-pp-cli when you need to reason about your Render footprint as a whole, not one resource at a time. It shines for env-var promotion across environments, blueprint drift checks in CI, monthly cost rollups, preview cleanup, and audit-log forensics. For one-off interactive workflows like render psql or render ssh, the official CLI is fine — render-pp-cli covers those too but its real value is the analytical commands the dashboard hides.

Unique Capabilities

These capabilities aren't available in any other tool for this API.

Local state that compounds

• env diff — Compare env vars between any two services, env-groups, or a service vs an env-group, three-way diff style.

  Reach for this when promoting config across environments — it's the cheapest way to see what's actually different without click-through.

  render-pp-cli env diff srv-staging-api srv-prod-api --json

• env promote — Copy env vars from a source service or env-group to a target with --only/--exclude/--dry-run.

  Use when shipping a known-good staging config to prod without dragging dev-only keys along.

  render-pp-cli env promote --from srv-staging-api --to srv-prod-api --exclude DEBUG_TOKEN --dry-run

• drift — Compare a checked-in render.yaml against live workspace state and report added/removed/modified entities by name.

  Run this in CI to fail builds when someone edits prod through the dashboard instead of the blueprint.

  render-pp-cli drift --blueprint render.yaml --json

• cost — Sum monthly cost across services, postgres, key-value, redis, and disks; group by project, environment, or owner.

  Reach for this on the Friday cost-review or when finance asks 'what would happen if we downsized these three services?'

  render-pp-cli cost --group-by project --json

• rightsize — For each service, fetch last --since 7d of CPU and memory; compute p95 utilization; flag services breaching --high or --low thresholds against plan capacity.

  Run this before the cost rollup to find quick downsizing wins or services about to throttle.

  render-pp-cli rightsize --since 7d --high 80 --low 20 --json

Lifecycle hygiene

• preview-cleanup — List preview services older than --stale-days N; delete in bulk on --confirm.

  Use when the monthly bill spikes and you suspect orphaned preview envs.

  render-pp-cli preview-cleanup --stale-days 14 --confirm

• orphans — Find unattached disks, empty env-groups, custom-domains pointing at deleted services, registry credentials referenced by no service, and disk snapshots beyond retention.

  Audit cleanup, billing review, and SOC 2 evidence-gathering all start here.

  render-pp-cli orphans --json

Agent-native plumbing

• env where — For a given env-var key, list every service and env-group that defines it with hash, length, and last-modified timestamp (never raw value).

  First call during a credential rotation or a 'who uses this secret' audit.

  render-pp-cli env where STRIPE_KEY --json

• incident-timeline — Merge deploys, events, and audit-logs for one service into one chronological table for a given window.

  First command on-call should run during a 2am page after a deploy.

  render-pp-cli incident-timeline srv-checkout-api --since 2h --json

• audit search — FTS5 search across cached audit logs by actor, target, action, and time window.

  Use during SOC 2 evidence-gathering or to answer 'who rotated this key last quarter'.

  render-pp-cli audit search --actor riley@example.com --target STRIPE_KEY --since 30d --json

• deploys diff — Show commit range, env-var changes, image-tag changes, and plan/region/scale changes between two deploys of one service.

  First command in a post-deploy regression triage — answers 'what actually changed'.

  render-pp-cli deploys diff srv-checkout-api dep-aaa dep-bbb --json

Command Reference

blueprints — Blueprints allow you to define your resources in a render.yaml file and automatically sync changes to your Render services. The API gives control over how your Blueprints are used to create and manage resources.

• render-pp-cli blueprints disconnect — Disconnect the Blueprint with the provided ID. Disconnecting a Blueprint stops automatic resource syncing via the...
• render-pp-cli blueprints list — List Blueprints for the specified workspaces. If no workspaces are provided, returns all Blueprints the API key has...
• render-pp-cli blueprints retrieve — Retrieve the Blueprint with the provided ID.
• render-pp-cli blueprints update — Update the Blueprint with the provided ID.
• render-pp-cli blueprints validate — Validate a render.yaml Blueprint file without creating or modifying any resources. This endpoint checks the syntax...

cron-jobs — Manage cron jobs

disks — Disks allow you to attach persistent storage to your services.

• render-pp-cli disks add — Attach a persistent disk to a web service, private service, or background worker. The service must be redeployed for...
• render-pp-cli disks delete — Delete a persistent disk attached to a service. All data on the disk will be lost. The disk's associated service...
• render-pp-cli disks list — List persistent disks matching the provided filters. If no filters are provided, returns all disks you have...
• render-pp-cli disks retrieve — Retrieve the persistent disk with the provided ID.
• render-pp-cli disks update — Update the persistent disk with the provided ID. The disk's associated service must be deployed and active for...

env-groups — Manage env groups

• render-pp-cli env-groups create — Create a new environment group.
• render-pp-cli env-groups delete — Delete the environment group with the provided ID, including all environment variables and secret files it contains.
• render-pp-cli env-groups list — List environment groups matching the provided filters. If no filters are provided, all environment groups are returned.
• render-pp-cli env-groups retrieve — Retrieve an environment group by ID.
• render-pp-cli env-groups update — Update the attributes of an environment group.

environments — Manage environments

• render-pp-cli environments create — Create a new environment belonging to the project with the provided ID.
• render-pp-cli environments delete — Delete the environment with the provided ID. Requires the environment to be empty (i.e., it must contain no services...
• render-pp-cli environments list — List a particular project's environments matching the provided filters. If no filters are provided, all environments...
• render-pp-cli environments retrieve — Retrieve the environment with the provided ID.
• render-pp-cli environments update — Update the details of the environment with the provided ID.

events — View events for a service, postgres or key value

• render-pp-cli events <eventId> — Retrieve the details of a particular event

key-value — Key Value allows you to interact with your Render Key Value instances.

• render-pp-cli key-value create — Create a new Key Value instance.
• render-pp-cli key-value delete — Delete a Key Value instance by ID.
• render-pp-cli key-value list — List Key Value instances matching the provided filters. If no filters are provided, all Key Value instances are...
• render-pp-cli key-value retrieve — Retrieve a Key Value instance by ID.
• render-pp-cli key-value update — Update a Key Value instance by ID.

logs — Logs allow you to retrieve logs for your services, Postgres databases, and redis instances. You can query for logs or subscribe to logs in real-time via a websocket.

• render-pp-cli logs delete-owner-stream — Removes the log stream for the specified workspace.
• render-pp-cli logs delete-resource-stream — Removes the log stream override for the specified resource. After deletion, the resource will use the workspace's...
• render-pp-cli logs get-owner-stream — Returns log stream information for the specified workspace.
• render-pp-cli logs get-resource-stream — Returns log stream override information for the specified resource. A log stream override takes precedence over a...
• render-pp-cli logs list — List logs matching the provided filters. Logs are paginated by start and end timestamps. There are more logs to...
• render-pp-cli logs list-resource-streams — Lists log stream overrides for the provided workspace that match the provided filters. These overrides take...
• render-pp-cli logs list-values — List all values for a given log label in the logs matching the provided filters.
• render-pp-cli logs subscribe — Open a websocket connection to subscribe to logs matching the provided filters. Logs are streamed in real-time as...
• render-pp-cli logs update-owner-stream — Updates log stream information for the specified workspace. All logs for resources owned by this workspace will be...
• render-pp-cli logs update-resource-stream — Updates log stream override information for the specified resource. A log stream override takes precedence over a...

maintenance — The Maintenance endpoints allow you to retrieve the latest maintenance runs for your Render services. You can also reschedule maintenance or trigger it to start immediately.

• render-pp-cli maintenance list — List scheduled and/or recent maintenance runs for specified resources.
• render-pp-cli maintenance retrieve — Retrieve the maintenance run with the provided ID.
• render-pp-cli maintenance update — Update the maintenance run with the provided ID. Updates from this endpoint are asynchronous. To check your update's...

metrics — The Metrics endpoints allow you to retrieve metrics for your services, Postgres databases, and redis instances.

• render-pp-cli metrics get-active-connections — Get the number of active connections for one or more Postgres databases or Redis instances.
• render-pp-cli metrics get-bandwidth — Get bandwidth usage for one or more resources.
• render-pp-cli metrics get-bandwidth-sources — Get bandwidth usage for one or more resources broken down by traffic source (HTTP, WebSocket, NAT, PrivateLink)....
• render-pp-cli metrics get-cpu — Get CPU usage for one or more resources.
• render-pp-cli metrics get-cpu-limit — Get the CPU limit for one or more resources.
• render-pp-cli metrics get-cpu-target — Get CPU target for one or more resources.
• render-pp-cli metrics get-disk-capacity — Get persistent disk capacity for one or more resources.
• render-pp-cli metrics get-disk-usage — Get persistent disk usage for one or more resources.
• render-pp-cli metrics get-http-latency — Get HTTP latency metrics for one or more resources.
• render-pp-cli metrics get-http-requests — Get the HTTP request count for one or more resources.
• render-pp-cli metrics get-instance-count — Get the instance count for one or more resources.
• render-pp-cli metrics get-memory — Get memory usage for one or more resources.
• render-pp-cli metrics get-memory-limit — Get the memory limit for one or more resources.
• render-pp-cli metrics get-memory-target — Get memory target for one or more resources.
• render-pp-cli metrics get-replication-lag — Get seconds of replica lag of a Postgres replica.
• render-pp-cli metrics get-task-runs-completed — Get the total number of task runs completed for one or more tasks. Optionally filter by state (succeeded/failed) or...
• render-pp-cli metrics get-task-runs-queued — Get the total number of task runs queued for one or more tasks.
• render-pp-cli metrics list-application-filter-values — List instance values to filter by for one or more resources.
• render-pp-cli metrics list-http-filter-values — List status codes and host values to filter by for one or more resources.
• render-pp-cli metrics list-path-filter-values — The path suggestions are based on the most recent 5000 log lines as filtered by the provided filters

metrics-stream — Manage metrics stream

• render-pp-cli metrics-stream delete-owner — Deletes the metrics stream for the specified workspace.
• render-pp-cli metrics-stream get-owner — Returns metrics stream information for the specified workspace.
• render-pp-cli metrics-stream upsert-owner — Creates or updates the metrics stream for the specified workspace.

notification-settings — Notification Settings allow you to configure which notifications you want to recieve, and where you will receive them.

• render-pp-cli notification-settings list-notification-overrides — List notification overrides matching the provided filters. If no filters are provided, returns all notification...
• render-pp-cli notification-settings patch-owner — Update notification settings for the owner with the provided ID.
• render-pp-cli notification-settings patch-service-notification-overrides — Update the notification override for the service with the provided ID.
• render-pp-cli notification-settings retrieve-owner — Retrieve notification settings for the owner with the provided ID. Note that you provide an owner ID to this...
• render-pp-cli notification-settings retrieve-service-notification-overrides — Retrieve the notification override for the service with the provided ID. Note that you provide a service ID to this...

organizations — Manage organizations

owners — Manage owners

• render-pp-cli owners list — List the workspaces that your API key has access to, optionally filtered by name or owner email address.
• render-pp-cli owners retrieve — Retrieve the workspace with the provided ID. Workspace IDs start with tea-. If you provide a user ID (starts with...

postgres — Postgres endpoints enable you to interact with your Render Postgres databases. You can manage databases, exports, recoveries, and failovers.

• render-pp-cli postgres create — Create a new Postgres instance.
• render-pp-cli postgres delete — Delete a Postgres instance by ID. This operation is irreversible, and all data will be lost.
• render-pp-cli postgres list — List Postgres instances matching the provided filters. If no filters are provided, all Postgres instances are returned.
• render-pp-cli postgres retrieve — Retrieve a Postgres instance by ID.
• render-pp-cli postgres update — Update a Postgres instance by ID.

projects — Manage projects

• render-pp-cli projects create — Create a new project.
• render-pp-cli projects delete — Delete the project with the provided ID. Requires all of the project's environments to be empty (i.e., they must...
• render-pp-cli projects list — List projects matching the provided filters. If no filters are provided, all projects are returned.
• render-pp-cli projects retrieve — Retrieve the project with the provided ID.
• render-pp-cli projects update — Update the details of a project. To update the details of a particular environment in the project, instead use the...