From 1df72643e1606f0b953dd1c974c168fedf22f930 Mon Sep 17 00:00:00 2001 From: Aloys Jehwin Date: Thu, 27 Aug 2026 22:42:36 +0530 Subject: [PATCH] fix(deploy.sh): initialise ENABLE_MODEL_ARMOR_FLAG before the regime gate The only two assignments were inside the FEDRAMP_HIGH/NONE branch, but the value is consumed unconditionally by jq --argjson. Under IL4/IL5 the variable was unset, so jq got an empty argument and set -e aborted the script part-way through configuring applications. Initialising per iteration also stops a previous app's answer leaking into the next one. Fixes #177 Signed-off-by: Aloys Jehwin --- blueprints/fedramp-high/gemini-enterprise/deploy.sh | 1 + 1 file changed, 1 insertion(+) diff --git a/blueprints/fedramp-high/gemini-enterprise/deploy.sh b/blueprints/fedramp-high/gemini-enterprise/deploy.sh index def61e912..d896c06f2 100755 --- a/blueprints/fedramp-high/gemini-enterprise/deploy.sh +++ b/blueprints/fedramp-high/gemini-enterprise/deploy.sh @@ -1350,6 +1350,7 @@ prompt_gemini_apps() { ENABLE_AGENT_SHARING_NO_APPROVAL_FLAG="false" fi + ENABLE_MODEL_ARMOR_FLAG="false" if [[ "$COMPLIANCE_REGIME" == "FEDRAMP_HIGH" || "$COMPLIANCE_REGIME" == "NONE" ]]; then echo "" echo -e "${YELLOW}Model Armor Feature:${NC}"