Skip to content

fix: simplify check for ACI deployment in custom deployment#804

Open
Ragini-Microsoft wants to merge 1 commit intodevfrom
rc-custom-dev
Open

fix: simplify check for ACI deployment in custom deployment#804
Ragini-Microsoft wants to merge 1 commit intodevfrom
rc-custom-dev

Conversation

@Ragini-Microsoft
Copy link
Copy Markdown
Collaborator

@Ragini-Microsoft Ragini-Microsoft commented Apr 8, 2026

Purpose

This pull request simplifies the deployment logic in the azure_custom.yaml file by removing unnecessary checks when determining if this is the first deployment. The main change is that the script now only checks for the existence of the AZURE_CONTAINER_REGISTRY_NAME environment variable, rather than also checking the value of IMAGE_TAG.

Deployment script simplification:

  • Removed the additional check for IMAGE_TAG being not equal to 'latest' in both the PowerShell and Bash deployment hooks, so the script now only checks for the absence of AZURE_CONTAINER_REGISTRY_NAME to determine if this is the first deployment. [1] [2]

Does this introduce a breaking change?

  • Yes
  • No

Golden Path Validation

  • I have tested the primary workflows (the "golden path") to ensure they function correctly without errors.

Deployment Validation

  • I have validated the deployment process successfully and all services are running as expected with this change.

@Ragini-Microsoft Ragini-Microsoft changed the base branch from main to dev April 8, 2026 15:23
@Ragini-Microsoft Ragini-Microsoft changed the title Enhance Bastion and Jumpbox deployment with VM size recommendations fix: simplify check for ACI deployment in custom deployment Apr 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant