unoverse 0.1.67 → 0.1.68
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/operator/lib/deploy.sh +5 -1
- package/package.json +1 -1
package/operator/lib/deploy.sh
CHANGED
|
@@ -12,7 +12,11 @@
|
|
|
12
12
|
# away, and the SAVED plan is what runs, so what was approved is what happens. Identical
|
|
13
13
|
# for every cloud: the summary reads the plan JSON, which is provider-agnostic.
|
|
14
14
|
_ground_apply() {
|
|
15
|
-
local cloud="$1"
|
|
15
|
+
local cloud="$1" tmp planfile rc
|
|
16
|
+
# SEPARATE STATEMENT. On macOS bash 3.2 a single `local a="$1" b="...$a"` expands $a
|
|
17
|
+
# EMPTY, so dir became "$ROOT/infra/" and terraform answered "No configuration files".
|
|
18
|
+
# Same trap that once made the release publish the repo root.
|
|
19
|
+
local dir="$ROOT/infra/$cloud"
|
|
16
20
|
tmp=$(mktemp -d); planfile="$tmp/plan"
|
|
17
21
|
|
|
18
22
|
terraform -chdir="$dir" init -input=false >/dev/null 2>&1 || { fail "terraform init failed"; rm -rf "$tmp"; return 1; }
|
package/package.json
CHANGED