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) <noreply@anthropic.com>
This commit is contained in:
parent
8a7491d3e0
commit
72aabe7d9a
@ -835,9 +835,7 @@ def create_operation(
|
|||||||
# Copy from temp to deployment dir, excluding data volumes
|
# Copy from temp to deployment dir, excluding data volumes
|
||||||
# and backing up changed files.
|
# and backing up changed files.
|
||||||
# Exclude data/* to avoid touching user data volumes.
|
# Exclude data/* to avoid touching user data volumes.
|
||||||
# Exclude config file to preserve deployment settings
|
exclude_patterns = ["data", "data/*"]
|
||||||
# (XXX breaks passing config vars from spec)
|
|
||||||
exclude_patterns = ["data", "data/*", constants.config_file_name]
|
|
||||||
_safe_copy_tree(
|
_safe_copy_tree(
|
||||||
temp_dir, deployment_dir_path, exclude_patterns=exclude_patterns
|
temp_dir, deployment_dir_path, exclude_patterns=exclude_patterns
|
||||||
)
|
)
|
||||||
|
|||||||
Loading…
Reference in New Issue
Block a user