Skip to content

refactor: move environment into the service-key registry#64

Merged
lesnik512 merged 3 commits into
mainfrom
environment-into-registry
Jul 15, 2026
Merged

refactor: move environment into the service-key registry#64
lesnik512 merged 3 commits into
mainfrom
environment-into-registry

Conversation

@lesnik512

Copy link
Copy Markdown
Member

Moves the compose environment service key into the SERVICE_KEYS registry as _map("-e"), deleting its hand-rolled validate (parsing._validate_environment), the -e branch of emit._env_flags (renamed _env_file_flags), and its entry in extends._STRUCTURAL_MERGE_KEYS / keys.STRUCTURAL_KEYS. environment now has the same single-spec locality (validate + emit + merge in one place) and drift-immunity as its map-shaped twins labels/annotations.

Behavior-preserving. The -e KEY=val tokens are byte-identical; podman env precedence is by source not command-line order (--env always beats --env-file, per podman-run.1), so -e moving after --env-file in the generated script is inert. The one observable change is the extends error message for a malformed side, now the registry-standard 'environment' must be a list or mapping — the drift-close this move exists to deliver.

Rationale and design: planning/changes/2026-07-15.17-environment-into-registry.md.
Sits under the narrow revisit licensed by planning/decisions/2026-07-12-reject-structural-key-registry.md (a single-key move, not a structural-key registry).

Gates: just test-ci 1261 passed @ 100% coverage · just lint-ci clean · just check-planning OK. architecture/supported-subset.md promoted in the same PR.

🤖 Generated with Claude Code

@lesnik512 lesnik512 merged commit cc995db into main Jul 15, 2026
8 checks passed
@lesnik512 lesnik512 deleted the environment-into-registry branch July 15, 2026 20:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant