Skip to content

Enhance Azure Government support and live test configurations#2573

Draft
jairmyree wants to merge 14 commits intomainfrom
features/gov-test
Draft

Enhance Azure Government support and live test configurations#2573
jairmyree wants to merge 14 commits intomainfrom
features/gov-test

Conversation

@jairmyree
Copy link
Copy Markdown
Member

This pull request introduces significant improvements to the test infrastructure, enabling support for running tests in sovereign Azure clouds (such as AzureUSGovernment) and providing more flexible test selection in CI pipelines. The changes include new pipeline parameters, environment propagation throughout test scripts, and configuration updates to support government cloud testing.

Pipeline and Test Infrastructure Enhancements

  • Added GovTest and RunAllLiveTests boolean parameters to pipeline templates (common.yml, build.yml) and ensured these propagate as variables, enabling selective execution of government cloud tests and all live tests. [1] [2] [3] [4] [5] [6]
  • Updated the live test job template (live-test.yml) to use the correct Azure service connection, set the Environment variable (AzureCloud or AzureUSGovernment), and pass this through to resource deployment and test scripts. [1] [2] [3] [4] [5]

Test Script and Resource Deployment Updates

  • Modified PowerShell scripts (Deploy-TestResources.ps1, Test-Code.ps1, test resource post scripts) to accept and propagate the Environment parameter, ensuring deployed resources and tests run in the correct cloud context. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12]
  • Updated logic in New-BuildInfo.ps1 to respect the new pipeline parameters and adjust which tests run on pull requests. [1] [2]

Configuration and Cloud Environment Support

  • Improved cloud environment detection in AzureCloudConfiguration.cs to prioritize configuration keys and environment variables in a case-insensitive manner.
  • Added a dataLocation property to the AzureUSGovernment.json test resource configuration file for better environment targeting.

Project and Solution File Maintenance

  • Updated the solution file Azure.Mcp.Server.slnx to correctly reference both unit and live test projects.

These changes collectively enable robust, environment-aware test execution across multiple Azure clouds, with enhanced control for CI/CD scenarios.

hallipr and others added 14 commits May 6, 2026 15:42
…onsumption plan for gov cloud compatibility

Flex Consumption (FC1) is not available in Azure US Government subscriptions.
Replace with a standard Y1/Dynamic consumption plan with reserved=true for Linux,
using conventional appSettings including WEBSITE_CONTENTAZUREFILECONNECTIONSTRING,
WEBSITE_CONTENTSHARE, FUNCTIONS_WORKER_RUNTIME, WEBSITE_RUN_FROM_PACKAGE, and
linuxFxVersion instead of the Flex-specific functionAppConfig block.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
… endpoint suffix handling and provisioner OID parameter
…2374)

* Add Environment to live-test.yml

* Clean up AzureCloudConfiguration parsing.

* Pass Environment to test

* Update Aks VM image

* Add Environment to test-resources-post

* Fix test code parameter name

* Add Environment parameter.

* Remove Dogfood type

* Fix casing

* Remove Azure.Mcp.Server.LiveTests -> They've been consolidated into Azure.Mcp.Core.LiveTests
- Introduced AzureCloud enum to identify target cloud environments in LiveTestSettings.
- Updated various tests to skip or adapt based on the Azure cloud type, particularly for US Government and China clouds.
- Modified service endpoints and API versions in AppServiceService and other services to ensure compatibility across different Azure clouds.
- Refactored location handling in ComputeCommandTests and StorageCommandTests to use dynamic location retrieval.
- Added outputs for location in Bicep files for EventHubs and Storage resources.
@jairmyree jairmyree force-pushed the features/gov-test branch from fed21e2 to 27e6e4d Compare May 6, 2026 19:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: Untriaged

Development

Successfully merging this pull request may close these issues.

3 participants