amsd-pipeline 1.14.0 → 1.16.0

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.
Files changed (2) hide show
  1. package/install.sh +8 -0
  2. package/package.json +1 -1
package/install.sh CHANGED
@@ -248,6 +248,14 @@ if [ -n "$DEST" ]; then
248
248
  restore_operator_config "$DEST" "$_OPCFG_TMP"
249
249
  rm -rf "$_OPCFG_TMP"
250
250
  fi
251
+ # THE EXCLUDES ABOVE MEAN TAR NEVER CREATES THESE PATHS, FRESH INSTALL INCLUDED — see
252
+ # run_state_ensure_dirs in lib/preserve-run-state.sh for why that is a real defect (root-owned
253
+ # orchestrations/logs, confirmed live 2026-09-04) and not just "nothing to restore yet". Created
254
+ # here, owned by the operator running this installer, before Docker or anything else can create
255
+ # one of them first under a different identity.
256
+ if [ -f "$INSTALLER_DIR/run-state-paths.json" ]; then
257
+ run_state_ensure_dirs "$INSTALLER_DIR/run-state-paths.json" "$DEST"
258
+ fi
251
259
  _ok "packaged $_PKG_REF into $DEST"
252
260
  ROOT="$DEST"
253
261
  CONFIG="$ROOT/orchestrations/config"
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "amsd-pipeline",
3
- "version": "1.14.0",
3
+ "version": "1.16.0",
4
4
  "description": "Installer for the amsd-pipeline orchestration stack. Clones, packages and provisions the full stack with one command — no separate git clone step.",
5
5
  "bin": {
6
6
  "amsd-pipeline": "bin/amsd-pipeline.js"