pin PROMOTIONS_FILE on cart deployments
Build and Publish / BuildAndDeployAmd64 (push) Failing after 3s
Build and Publish / BuildAndDeployArm64 (push) Failing after 5s

Cart-actor (x86/arm64) and cart-backoffice all resolve to the same NFS file at nfs/cart-actor/promotions.json given their existing volume mounts. cart-actor pods use PROMOTIONS_FILE=/data/promotions.json (mount subpath); cart-backoffice uses /data/cart-actor/promotions.json (NFS root + CART_DIR). Defensive alignment so UI edits are visible across pods even if a future NFS subpath shuffle happens.
This commit is contained in:
2026-07-04 12:41:36 +02:00
parent 31530be28f
commit 6180706140
+6
View File
@@ -78,6 +78,8 @@ spec:
env: env:
- name: CART_DIR - name: CART_DIR
value: "/data/cart-actor" value: "/data/cart-actor"
- name: PROMOTIONS_FILE
value: "/data/cart-actor/promotions.json"
- name: CHECKOUT_DIR - name: CHECKOUT_DIR
value: "/data/checkout-actor" value: "/data/checkout-actor"
- name: TZ - name: TZ
@@ -186,6 +188,8 @@ spec:
env: env:
- name: CART_DIR - name: CART_DIR
value: "/data/cart-actor" value: "/data/cart-actor"
- name: PROMOTIONS_FILE
value: "/data/promotions.json"
- name: CHECKOUT_DIR - name: CHECKOUT_DIR
value: "/data/checkout-actor" value: "/data/checkout-actor"
- name: TZ - name: TZ
@@ -312,6 +316,8 @@ spec:
memory: "70Mi" memory: "70Mi"
cpu: "1200m" cpu: "1200m"
env: env:
- name: PROMOTIONS_FILE
value: "/data/promotions.json"
- name: TZ - name: TZ
value: "Europe/Stockholm" value: "Europe/Stockholm"
- name: REDIS_ADDRESS - name: REDIS_ADDRESS