From 72aabe7d9ae94fbffecb3ea05dfcbbf6689e7340 Mon Sep 17 00:00:00 2001 From: "A. F. Dudley" Date: Tue, 17 Mar 2026 08:20:45 +0000 Subject: [PATCH] fix: deploy create --update now syncs config.env from spec The --update path excluded config.env from the safe_copy_tree, which meant new config vars added to spec.yml were never written to config.env. The XXX comment already flagged this as broken. Remove config.env from exclude_patterns so --update regenerates it from spec.yml like the non-update path does. Co-Authored-By: Claude Opus 4.6 (1M context) --- stack_orchestrator/deploy/deployment_create.py | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/stack_orchestrator/deploy/deployment_create.py b/stack_orchestrator/deploy/deployment_create.py index 792d8e3d..5593c60b 100644 --- a/stack_orchestrator/deploy/deployment_create.py +++ b/stack_orchestrator/deploy/deployment_create.py @@ -835,9 +835,7 @@ def create_operation( # Copy from temp to deployment dir, excluding data volumes # and backing up changed files. # Exclude data/* to avoid touching user data volumes. - # Exclude config file to preserve deployment settings - # (XXX breaks passing config vars from spec) - exclude_patterns = ["data", "data/*", constants.config_file_name] + exclude_patterns = ["data", "data/*"] _safe_copy_tree( temp_dir, deployment_dir_path, exclude_patterns=exclude_patterns )