Skip to content

feat: support the service container_name key#12

Merged
lesnik512 merged 2 commits into
mainfrom
feat/container-name
Jul 8, 2026
Merged

feat: support the service container_name key#12
lesnik512 merged 2 commits into
mainfrom
feat/container-name

Conversation

@lesnik512

Copy link
Copy Markdown
Member

Accepts container_name, resolved to loopback exactly like the already-shipped hostname support (#8): folded into graph.hostnames() -> --add-host <name>:127.0.0.1. The real podman container name stays {pod}-{service} (unchanged) — only DNS-style resolution is affected, per the reporting user's confirmation that the name is also used as a hostname.

Independently reviewed: ready to merge, no findings.

Design/spec: planning/changes/2026-07-08.03-container-name.md. architecture/supported-subset.md updated in this PR.

Tests

just test-ci — 92 passed, 100% line coverage. just lint-ci clean.

lesnik512 added 2 commits July 8, 2026 17:48
Mirrors the existing hostname support: container_name is accepted in
validate() and folded into graph.hostnames(), so it becomes an
--add-host <name>:127.0.0.1 entry. The actual podman container is still
named {pod}-{service} internally; only name resolution is affected.
@lesnik512 lesnik512 merged commit 2a9528b into main Jul 8, 2026
6 checks passed
@lesnik512 lesnik512 deleted the feat/container-name branch July 8, 2026 14:54
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