Bug Description
Once a matching Assured Workloads folder is found, gemini-enterprise/deploy.sh (~Lines 1420–1434) always prints ACTION REQUIRED: Please update your Assured Workload environment manually and, after the operator presses Enter, Assured Workload folder <name> validated / updated. The underlying gcloud assured workloads list call only fetches the workload displayName — it never queries update or violation status — so the "ACTION REQUIRED" nag fires every run even when nothing is pending, and the "validated / updated" confirmation is cosmetic. The following Access Transparency prompt is the same unconditional acknowledge-nudge.
Environment and Deployment Context
- Stellar Engine Version/Commit:
main @ 3728fc98
- Deployment Type:
- Affected Component:
blueprints/fedramp-high/gemini-enterprise/deploy.sh — Assured Workloads check (~Lines 1420–1434) and the adjacent Access Transparency acknowledge prompt
Steps to Reproduce
- Run
./deploy.sh (Brownfield, Step 1) on any tenant with an existing, healthy Assured Workloads folder.
- Observe
ACTION REQUIRED: Please update your Assured Workload environment manually even though no update is pending.
- Press Enter; observe the cosmetic
Assured Workload folder <name> validated / updated line.
Expected Behavior
Only prompt when updates actually exist (query workload update/violation status), or reword to "please verify" and drop the false "validated / updated" confirmation.
Actual Behavior
Every run shows a false ACTION REQUIRED plus a false success line, training operators to ignore a message that could one day be real.
Relevant Logs and Errors
ACTION REQUIRED: Please update your Assured Workload environment manually
Press Enter to continue...
Assured Workload folder <name> validated / updated
Bug Description
Once a matching Assured Workloads folder is found,
gemini-enterprise/deploy.sh(~Lines 1420–1434) always printsACTION REQUIRED: Please update your Assured Workload environment manuallyand, after the operator presses Enter,Assured Workload folder <name> validated / updated. The underlyinggcloud assured workloads listcall only fetches the workload displayName — it never queries update or violation status — so the "ACTION REQUIRED" nag fires every run even when nothing is pending, and the "validated / updated" confirmation is cosmetic. The following Access Transparency prompt is the same unconditional acknowledge-nudge.Environment and Deployment Context
main@3728fc98blueprints/fedramp-high/gemini-enterprise/deploy.sh— Assured Workloads check (~Lines 1420–1434) and the adjacent Access Transparency acknowledge promptSteps to Reproduce
./deploy.sh(Brownfield, Step 1) on any tenant with an existing, healthy Assured Workloads folder.ACTION REQUIRED: Please update your Assured Workload environment manuallyeven though no update is pending.Assured Workload folder <name> validated / updatedline.Expected Behavior
Only prompt when updates actually exist (query workload update/violation status), or reword to "please verify" and drop the false "validated / updated" confirmation.
Actual Behavior
Every run shows a false ACTION REQUIRED plus a false success line, training operators to ignore a message that could one day be real.
Relevant Logs and Errors