Render Deploy Diff — 技能 — openclaw中文资讯站

技能详情（站内镜像，无评论）

Detect config drift between required local env keys and a Render service before deploy; fails when required keys are missing remotely.

开发与 DevOps

作者：Daniel Lummis @daniellummis

许可证：MIT-0

MIT-0 ·免费使用、修改和重新分发。无需归因。

版本：v1.0.0

统计：⭐ 0 · 163 · 0 current installs · 0 all-time installs

⭐ 0

安装量（当前） 0

🛡 VirusTotal ：良性 · OpenClaw ：良性

Package：daniellummis/render-deploy-diff

安全扫描（ClawHub）

VirusTotal ：良性
OpenClaw ：良性

OpenClaw 评估

The skill does what it claims (compare local required env keys to a Render service) and requests only the Render API key and common CLI tools; nothing in the code suggests hidden behavior.

目的

Name/description match the script and SKILL.md. Required binaries (bash, curl, python3) and RENDER_API_KEY are reasonable and proportionate for querying the Render API and parsing local files.

说明范围

The runtime instructions and script only read explicit local env template files (default .env.example,.env.production or files you pass), optional offline JSON, and call the Render API to fetch env-vars. They do not attempt to read other system paths. Note: the script supports an override RENDER_API_BASE_URL (for testing) which means requests (and the Authorization header) will be sent to whatever URL you configure.

安装机制

Instruction-only skill with an included shell script; no installation, downloads, or archive extraction. This has a low install risk surface.

证书

Only RENDER_API_KEY is required. Other inputs (SERVICE_ID/NAME, REQUIRED_ENV_KEYS/FILES, RENDER_ENV_VARS_JSON_PATH, RENDER_API_BASE_URL) are optional and make sense for the stated use-cases (live vs offline testing). Be aware RENDER_API_BASE_URL can redirect the token to an arbitrary endpoint if set by the user.

持久

The skill does not request persistent presence (always is false), does not modify other skills or system configuration, and does not write persistent secrets.

综合结论

This skill appears coherent and implements its stated purpose. Before using it: (1) avoid pointing RENDER_API_BASE_URL at untrusted endpoints — the script will send your RENDER_API_KEY as a Bearer token to that URL; (2) prefer offline testing with RENDER_ENV_VARS_JSON_PATH when possible; (3) limit the privileges of the Render API key you provide (use a token with minimal required scope if possible); and (4) review any local .env.* files you al…

安装（复制给龙虾 AI）

将下方整段复制到龙虾中文库对话中，由龙虾按 SKILL.md 完成安装。

请把本段交给龙虾中文库（龙虾 AI）执行：为本机安装 OpenClaw 技能「Render Deploy Diff」。简介：Detect config drift between required local env keys and a Render service before…。
请 fetch 以下地址读取 SKILL.md 并按文档完成安装：https://raw.githubusercontent.com/openclaw/skills/refs/heads/main/skills/daniellummis/render-deploy-diff/SKILL.md
（来源：yingzhi8.cn 技能库）

SKILL.md

打开原始 SKILL.md（GitHub raw）

---
name: render-deploy-diff
description: Detect config drift between required local env keys and a Render service before deploy; fails when required keys are missing remotely.
version: 1.0.0
metadata: {"openclaw":{"requires":{"bins":["bash","curl","python3"],"env":["RENDER_API_KEY"]}}}
---

# Render Deploy Diff

Use this skill before deploy to compare required environment keys with what is currently configured on a Render service.

## What this skill does
- Resolves a target Render service by `RENDER_SERVICE_ID` or `RENDER_SERVICE_NAME`
- Reads required env keys from `REQUIRED_ENV_KEYS` or local env template files
- Fetches configured env keys from Render API
- Prints two drift sets:
  - required but missing on Render
  - present on Render but not required locally
- Exits non-zero when required keys are missing on Render

## Inputs
- `RENDER_API_KEY` (required unless using mock JSON)
- one of:
  - `RENDER_SERVICE_ID`
  - `RENDER_SERVICE_NAME`
- optional:
  - `RENDER_API_BASE_URL` (default `https://api.render.com/v1`)
  - `REQUIRED_ENV_KEYS` (comma-separated explicit required keys)
  - `REQUIRED_ENV_FILES` (comma-separated files to parse, default `.env.example,.env.production`)
  - `RENDER_ENV_VARS_JSON_PATH` (path to saved Render env-var API JSON for offline testing)

## Run

```bash
bash scripts/render-deploy-diff.sh
```

With explicit required keys:

```bash
RENDER_SERVICE_NAME=my-service 
REQUIRED_ENV_KEYS="DATABASE_URL,DIRECT_URL,SHADOW_DATABASE_URL,NEXT_PUBLIC_APP_URL" 
bash scripts/render-deploy-diff.sh
```

Offline test with saved API response:

```bash
REQUIRED_ENV_KEYS="DATABASE_URL,NEXT_PUBLIC_APP_URL" 
RENDER_ENV_VARS_JSON_PATH=./fixtures/render-env-vars.json 
bash scripts/render-deploy-diff.sh
```

## Output contract
- Prints service identity, required key count, remote key count, and drift summary
- Returns exit code `0` when all required keys exist on Render
- Returns exit code `1` when required keys are missing or inputs are invalid