unoverse 0.1.60 → 0.1.62

package/operator/lib/deploy.sh

@@ -18,6 +18,28 @@ cmd_deploy() {
     done
   fi
 
+  # INFRA CHANGES SHIP TOO. If the ground has pending changes (edited tfvars, a new
+  # resource in main.tf from an update), deploy applies them first — through
+  # terraform's own plan-and-yes gate — then re-renders the env, since outputs may
+  # have changed. Without this, deploy only ever shipped images once a server
+  # existed, and infrastructure edits silently rotted.
+  local g_applied
+  if command -v terraform >/dev/null 2>&1; then
+    local g rc
+    for g in digitalocean aws; do
+      [ -d "$ROOT/infra/$g/.terraform" ] || continue
+      terraform -chdir="$ROOT/infra/$g" plan -input=false -detailed-exitcode >/dev/null 2>&1
+      rc=$?
+      if [ "$rc" = "2" ]; then
+        info "Your $g infrastructure has pending changes"
+        terraform -chdir="$ROOT/infra/$g" apply || { fail "apply did not complete. Re-run: unoverse deploy"; exit 1; }
+        terraform -chdir="$ROOT/infra/$g" output -raw env_production > "$env_prod" 2>/dev/null           && ok "Refreshed .env.production from the ground"
+        g_applied=1
+      fi
+      break
+    done
+  fi
+
   # Missing .env.production is not an error if a ground has been applied — the
   # file is just a Terraform output, so render it ourselves. Reading state is
   # not wrapping terraform: apply stays the developer's explicit act.
@@ -109,16 +131,12 @@ cmd_deploy() {
     fi
     ok "terraform.tfvars is complete"
 
-    # PROVISION FROM RIGHT HERE, if wanted. terraform apply prints its plan and asks
-    # for its own explicit yes — creating billable infrastructure stays a deliberate,
-    # visible act, it just no longer requires leaving the flow.
+    # STRAIGHT INTO TERRAFORM. Its plan plus its own typed "yes" IS the decision gate
+    # for billable infrastructure; a [Y/n] in front of it was asking permission to ask
+    # permission. Answering "no" is terraform's "no".
+    echo ""
+    info "Provisioning. Terraform shows the plan and asks for your ${BOLD}yes${NC} before creating anything"
     echo ""
-    local REPLY
-    read -r -p "  Provision now? terraform runs here and shows its plan first. [Y/n] " REPLY
-    if [[ "$REPLY" =~ ^[Nn]$ ]]; then
-      info "When ready:  cd infra/$cloud && terraform init && terraform apply && cd ../.. && unoverse deploy"
-      exit 0
-    fi
     # Terraform is one static binary: install it directly from the official release
     # rather than sending anyone to brew (whose compile chain can demand Xcode Command
     # Line Tools updates for a tool that needs no compiling).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "unoverse",
-  "version": "0.1.60",
+  "version": "0.1.62",
   "description": "The Unoverse front door — create a Studio project, a universe, or a client app, and launch Studio.",
   "license": "SEE LICENSE IN README.md",
   "type": "module",