Add NSP + Storage + KeyVault deployment E2E test#16027
Add NSP + Storage + KeyVault deployment E2E test#16027mitchdenny merged 3 commits intomicrosoft:mainfrom
Conversation
Adds a new deployment test that: - Uses the Starter App (ASP.NET Core/React) template - Adds Azure Container Apps environment - Adds Azure Storage (with Blobs) and Azure Key Vault - Creates a Network Security Perimeter (NSP) with a subscription-level inbound access rule for the current Azure subscription - Associates both Storage and Key Vault with the NSP - Wires the ASP.NET Core backend (ApiService) to connect to both Storage Blobs and Key Vault - Deploys to Azure and verifies the endpoints work This tests the end-to-end NSP flow added in PR microsoft#15711. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
🚀 Dogfood this PR with:
curl -fsSL https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 16027Or
iex "& { $(irm https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 16027" |
|
/deployment-test |
|
🚀 Deployment tests starting on PR #16027... This will deploy to real Azure infrastructure. Results will be posted here when complete. |
|
🚀 Deployment tests starting on PR #16027... This will deploy to real Azure infrastructure. Results will be posted here when complete. |
There was a problem hiding this comment.
Pull request overview
Adds a new Azure deployment end-to-end test to validate Network Security Perimeter (NSP) behavior with Azure Storage (Blobs) and Azure Key Vault when deployed via aspire deploy, using the Starter App (ASP.NET Core/React) template.
Changes:
- Introduces a new E2E deployment test that provisions ACA + Storage + Key Vault + NSP and validates external endpoints are reachable post-deploy.
- Updates the generated AppHost to associate Storage and Key Vault with an NSP and adds subscription-based inbound access rules.
- Updates the generated ApiService to register Blob and Key Vault clients and wires those resources via
WithReference.
… prompt The az network perimeter list command can prompt to install an extension, causing the terminal to hang. Remove this non-essential verification step - NSP provisioning is already verified by the PIPELINE SUCCEEDED output. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
🚀 Deployment tests starting on PR #16027... This will deploy to real Azure infrastructure. Results will be posted here when complete. |
|
❌ Deployment E2E Tests failed — 20 passed, 10 failed, 0 cancelled View test results and recordings
|
|
/create-issue |
|
Failed tests found on this PR:
📋 Creates or updates a failing-test issue from CI failures. |
|
/create-issue Aspire.Cli.EndToEnd.Tests.PsCommandTests.PsCommandListsRunningAppHost |
Description
Adds a new deployment end-to-end test that validates the Azure Network Security Perimeter (NSP) feature added in #15711.
The test:
WithNetworkSecurityPerimeterWithReferenceaspire deployThis provides end-to-end coverage for the NSP feature, verifying that:
Checklist