[github-actions]

Problem

The rulesChatIndexImageTag parameter in infra/deploy.ps1 and infra/main.bicep was optional and defaulted to the site's imageTag. When running deploy.ps1 manually without providing -RulesChatIndexImageTag, the Rules Chat index job would be configured with an image tag that was never built or pushed. Only the automated deploy workflow builds and pushes rules-chat-index images, so manual deployments would fail to pull the image, and the failure would only be caught by the 2-day stale alert.

Solution

Made the RulesChatIndexImageTag parameter required in both:

• infra/deploy.ps1: Changed from optional with empty default to mandatory parameter
• infra/main.bicep: Removed the default value that fell back to imageTag

This ensures that:

1. Manual deploy.ps1 runs must explicitly provide the image tag
2. Deployment will fail early with a clear error if the tag is missing, rather than failing later when the job tries to pull a non-existent image
3. The parameter is always provided (either by the automated workflow or by manual invocation with the correct tag)

Changes

• infra/deploy.ps1:

  • Made -RulesChatIndexImageTag a mandatory parameter
  • Updated parameter documentation
  • Always pass the parameter to Bicep (removed conditional check)

• infra/main.bicep:

  • Removed the default value from rulesChatIndexImageTag parameter
  • Updated description to clarify that only the deploy workflow pushes this image

Acceptance Criteria

✅ A manual deploy.ps1 run cannot set the job to an image tag that does not exist (PowerShell will error if the parameter is not provided)

• Fixes 🐛 Bug - Rules chat index job image tag defaults to an image that nobody pushes #2786

Generated by Issue Triage for issue #2786 · ● 99.1K · ◷

[AntPolkanov]

Closing in favour of #2791, which fixes #2786 without making the tag mandatory. A mandatory tag would break PR slot deploys, because they pass an empty tag.