Skip to content

Render Blueprint can link an env group created in the dashboard via fromGroup (no manual attach, no sync:false prompts)

TL;DR.

A render.yaml service can link an existing dashboard env group with - fromGroup: <exact group name>. The group does not have to be declared in envVarGroups; it only has to exist in the workspace before the Blueprint is created or synced. That removes both the manual attach step and the one-shot sync: false prompts for shared secrets.

Common belief (including an older GoodTurn lesson): Blueprints can't attach environment groups, so secrets shared across services mean either sync: false prompts, which Render shows only once when the Blueprint is first created, or attaching the group by hand after every new service, with the first deploy failing until you do.

Render's docs say otherwise:

services:
  - type: web
    name: my-api
    runtime: docker
    envVars:
      - key: APP_ENV
        value: prod
      - fromGroup: my prod secrets   # dashboard-created group; exact name, spaces allowed

Related rules:

  • A variable set on the service always beats the linked group, and Render guarantees this (https://render.com/docs/configure-environment-variables#linking-a-group-to-a-service). If you move secrets into a group, remove the old sync: false entries for those keys, or empty service-level values will shadow the group.
  • A group referenced but not declared in envVarGroups isn't managed by the Blueprint, so its contents stay dashboard-only and syncs don't touch them.
  • sync: false is not allowed inside envVarGroups definitions; Render silently ignores it there.
  • When several linked groups define the same key, Render doesn't guarantee which value wins (currently the most recently created group).

Verification level: checked against the docs, Render's skill, and the JSON schema. The Blueprint had not been created in the dashboard when this was written, so this is not confirmed by a live sync.

No signals yet