[Dim145]

Checklist

• This PR is not opened from my fork’s main branch
• All new user-facing strings are translated via Paraglide (m.*())

What This PR Implements

Global variables can now be used for Compose ${VAR} substitution only, without being injected into every container. This also keeps secret global variables out of unrelated containers.

Addresses #3407 (discussion #4035). Replaces #4630, which was closed automatically when breaking/v3 was deleted.

Changes Made

• New per-variable injectIntoContainers flag: DB column, API create/update, CLI --inject, UI switch and "Injected" badge.
• Migration 00105 (Goose Go migration): existing variables are set to true, so upgrades keep the current behavior; new variables default to false.
• The effective set (env-scoped overrides included) marks interpolation-only keys with # arcane:noinject KEY lines in the .env.global header, ahead of every value. The env loader reads values and marks from the same read and skips marked keys when injecting.
• Materialized variables carry an optional per-variable noInject flag (omitted when false) in both the agent PUT and GET, so a re-added agent keeps its interpolation-only keys on import. Local .env.global is replaced atomically.

Testing Done

• New service/loader tests: flag defaults, scoped overrides, imported legacy variables, local materialization, agent payload, migration 105 up/down.
• A test loads every prefix of the generated .env.global and checks that an interpolation-only secret is never injected (the file is rewritten in place by truncate + write).
• golangci-lint (fmt + run) on backend/cli/types, vp fmt --check, eslint, svelte-check and Playwright tsc: all clean.
• Manual test in the dev environment: a substitution-only variable is resolved through ${VAR} but absent from the container env; an injected variable is present; toggling the flag and redeploying updates the container env; .env.global carries the # arcane:noinject marks ahead of the values.

AI Tool Used (if applicable)

Claude Code (Claude Opus 5.5) was used to implement the backend, CLI, frontend and tests, and to port the change onto v3. I reviewed the changes and tested them manually in the development environment.

Additional Context

• The materialized list holds non-injected keys: Huma rejects unknown properties, so the agent payload stays identical to the previous one while every key is injected, and an absent list means "inject everything".
• An agent older than this change will reject the sync (422, visible in the sync status) once a substitution-only variable is in its scope, instead of silently injecting it everywhere.
• If another PR lands migration 00104 first, I'll renumber this one.

Disclaimer Greptiles Reviews use AI, make sure to check over its work.

To better help train Greptile on our codebase, if the comment is useful and valid Like the comment, if its not helpful or invalid Dislike

To have Greptile Re-Review the changes, mention greptileai.

Confidence Score: 5/5

The PR appears safe to merge; the mounted-file sync issue is fixed.

Summary

Adds a per-variable choice between Compose substitution only and automatic container injection.

• Global variables can stay out of containers while Compose still uses them.

_{Reviews (4) · Last reviewed commit: "cr" · Reviewed by Greptile}