You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Route Makefile.terraform frontend-only through scripts/tf-deploy.sh (unify deploy paths) #59
After PR LeanerCloud/cloud-commitments-cli#1244 lands, scripts/tf-deploy.sh forwards arbitrary extra arguments verbatim to terraform, so -target=... is now a first-class capability of the script. The frontend-only target in Makefile.terraform, however, still bypasses the script and invokes terraform directly:
the colored banner / log_info / "Deployment Outputs" summary the script prints on success
the profile-existence validation (if [ ! -f "$PROFILE_FILE" ])
the environment-directory bootstrap (creates ${ENV_DIR} and symlinks main.tf if missing)
the terraform init auto-run when .terraform is absent
the AWS_PROFILE warning
A user who happens to run make frontend-only first will get a different (worse) experience than someone who runs make deploy first then make frontend-only. The duplication also means the path-arithmetic (../../../profiles/...) lives in two places.
Fix
Route frontend-only through the script now that the script supports -target=...:
Activity
IAmJSD commentedon Oct 23, 2026
Claiming: working on this
fix(scripts): route make frontend-only through tf-deploy.sh (LeanerCl…