From 68ef9de0161dbe5f2008eea3dbb91865928b3869 Mon Sep 17 00:00:00 2001 From: Prathamesh Musale Date: Tue, 10 Mar 2026 06:15:15 +0000 Subject: [PATCH] fix(k8s): resolve internal job compose files from data/compose-jobs resolve_job_compose_file() used Path(stack).parent.parent for the internal fallback, which resolved to data/stacks/compose-jobs/ instead of data/compose-jobs/. This meant deploy create couldn't find job compose files for internal stacks, so they were never copied to the deployment directory and never created as k8s Jobs. Use the same data directory resolution pattern as resolve_compose_file. Co-Authored-By: Claude Opus 4.6 --- stack_orchestrator/util.py | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/stack_orchestrator/util.py b/stack_orchestrator/util.py index 7e1e442c..3e0fb3f1 100644 --- a/stack_orchestrator/util.py +++ b/stack_orchestrator/util.py @@ -155,9 +155,8 @@ def resolve_job_compose_file(stack, job_name: str): if proposed_file.exists(): return proposed_file # If we don't find it fall through to the internal case - # TODO: Add internal compose-jobs directory support if needed - # For now, jobs are expected to be in external stacks only - compose_jobs_base = Path(stack).parent.parent.joinpath("compose-jobs") + data_dir = Path(__file__).absolute().parent.joinpath("data") + compose_jobs_base = data_dir.joinpath("compose-jobs") return compose_jobs_base.joinpath(f"docker-compose-{job_name}.yml")