Files
computer-playbook/module_utils/docker_paths_utils.py
T
kevinveenbirkenbach a55c99ef62 refactor(compose): replace docker lookup with container and unify compose paths
- Rename lookup plugin from `docker` to `container`
- Switch all lookups from `lookup('docker', ...)` to `lookup('container', ...)`
- Normalize compose file keys:
  - docker_compose → compose
  - docker_compose_override → compose_override
  - docker_compose_ca_override → compose_ca_override
- Centralize compose path resolution via docker_paths_utils
- Update compose_file_args to always derive paths from DIR_COMPOSITIONS
- Align all roles, templates, and vars with container/compose naming
- Update and rename unit tests accordingly

This prepares the codebase for engine-agnostic container backends
(e.g. Docker ↔ Podman) and removes legacy docker-specific assumptions.

https://chatgpt.com/share/6987a7cc-d374-800f-99ad-bb4c8f92c59e
2026-02-07 21:59:39 +01:00

31 lines
1.0 KiB
Python

# module_utils/docker_paths_utils.py
from __future__ import annotations
from module_utils.entity_name_utils import get_entity_name
def get_docker_paths(application_id: str, path_docker_compose_instances: str) -> dict:
"""
Build the compose dict based on path_docker_compose_instances and application_id.
Uses get_entity_name to extract the entity name from application_id.
"""
entity = get_entity_name(application_id)
base = f"{path_docker_compose_instances}{entity}/"
return {
"directories": {
"instance": base,
"env": f"{base}.env/",
"services": f"{base}services/",
"volumes": f"{base}volumes/",
"config": f"{base}config/",
},
"files": {
"env": f"{base}.env/env",
"compose": f"{base}compose.yml",
"compose_override": f"{base}compose.override.yml",
"compose_ca_override": f"{base}compose.ca.override.yml",
"dockerfile": f"{base}Dockerfile",
},
}