unoverse 0.1.131 → 0.1.132

package/operator/lib/deploy.sh

@@ -41,8 +41,12 @@
 # exists because the opposite mistake is what wiped this exact cluster's firewall once
 # already: an authoritative write that assumed the whole list was ours to own.
 _operator_db_access() {
-  local cloud="$1" dir="$ROOT/infra/$cloud" cluster
-  cluster=$(grep -E '^existing_pg_cluster_name[[:space:]]*=' "$dir/terraform.tfvars" 2>/dev/null | sed -E 's/.*"([^"]+)".*/\1/')
+  # `$2` is the cluster, when the CALLER already knows it. The monorepo has no ground to
+  # read one from — it develops against a cluster named only in .env — so re-deriving it
+  # from terraform.tfvars here meant this returned 0 and did nothing in the one place the
+  # developer actually types `npm run dev`.
+  local cloud="$1" dir="$ROOT/infra/$cloud" cluster="${2:-}"
+  [ -n "$cluster" ] || cluster=$(grep -E '^existing_pg_cluster_name[[:space:]]*=' "$dir/terraform.tfvars" 2>/dev/null | sed -E 's/.*"([^"]+)".*/\1/')
   [ -n "$cluster" ] || return 0
   [ -n "${DIGITALOCEAN_TOKEN:-}" ] || return 0
   mkdir -p "$ROOT/.unoverse"
@@ -108,16 +112,21 @@ cmd_db_allow() {
   # reachability is a VPC security group, owned by Terraform and changed by `deploy`, not by
   # a developer's laptop asking an API at runtime. Offering `db-allow aws` produced a
   # ground-picker prompt for a cloud that would then have done nothing.
-  SELF_CMD="unoverse db-allow" \
-  GROUNDS_ONLY="digitalocean" \
-  GROUNDS_ONLY_WHY="On AWS the database is reached through its VPC security group, which the ground owns — change it in infra/aws and run ${BOLD}unoverse deploy aws${NC}." \
-  cloud=$(_pick_ground "${1:-}") || {
-    [ -z "${1:-}" ] && [ ! -d "$ROOT/infra" ] && fail "No ground here. There is no database to reach"
-    return 1
-  }
+  # A GROUND IS OPTIONAL HERE. This used to `return 1` the moment the picker found none,
+  # which made the .env fallback below unreachable in the monorepo — the one checkout that
+  # has no ground and the one the fallback was written for. Only ask the picker when there
+  # is something to pick, so an ambiguous two-ground universe still stops, while a
+  # groundless checkout proceeds to look the cluster up where it actually knows it.
+  cloud=""
+  if ls "$ROOT"/infra/*/terraform.tfvars >/dev/null 2>&1; then
+    SELF_CMD="unoverse db-allow" \
+    GROUNDS_ONLY="digitalocean" \
+    GROUNDS_ONLY_WHY="On AWS the database is reached through its VPC security group, which the ground owns — change it in infra/aws and run ${BOLD}unoverse deploy aws${NC}." \
+    cloud=$(_pick_ground "${1:-}") || return 1
+  fi
 
-  local cluster
-  cluster=$(grep -E '^existing_pg_cluster_name[[:space:]]*=' "$ROOT/infra/$cloud/terraform.tfvars" 2>/dev/null | sed -E 's/.*"([^"]+)".*/\1/')
+  local cluster=""
+  [ -n "$cloud" ] && cluster=$(grep -E '^existing_pg_cluster_name[[:space:]]*=' "$ROOT/infra/$cloud/terraform.tfvars" 2>/dev/null | sed -E 's/.*"([^"]+)".*/\1/')
 
   # THE MONOREPO NEEDS THIS TOO, and it has no ground. The platform's own checkout is
   # developed against a managed cluster named only in .env, so a ground-only lookup found
@@ -147,7 +156,9 @@ cmd_db_allow() {
   fi
 
   echo ""
-  _operator_db_access "$cloud"
+  # Hand the cluster over: we already resolved it, from a ground OR from .env, and the
+  # helper cannot re-derive the .env case (there is no tfvars to read).
+  _operator_db_access "$cloud" "$cluster"
   echo ""
   info "Run this again whenever you change network"
   echo ""

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "unoverse",
-  "version": "0.1.131",
+  "version": "0.1.132",
   "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",