ci: enhance Azure deployment validation and enforce hosting model #1992
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose
This pull request enhances the CI/CD workflow for Azure deployments by improving deployment validation and configuration. The main improvements include adding automated checks to verify that deployed applications are running correctly (not just serving the default Azure page), setting the App Service hosting model explicitly, and providing clearer CI output.
Deployment verification and validation:
.github/workflows/ci.yml) that waits for services to stabilize, checks the frontend and admin URLs for availability, and ensures the deployed applications are not serving the default Azure page. If the default page is detected, the workflow fails, indicating a deployment issue.Configuration improvements:
AZURE_APP_SERVICE_HOSTING_MODELenvironment variable tocodein both the workflow (.github/workflows/ci.yml) and the deployment Makefile (Makefile). This ensures the correct hosting model is used during deployments. [1] [2]CI process clarity:
Does this introduce a breaking change?
How to Test
What to Check
Verify that the following are valid
Other Information