Enhance NSP deployment test with resource connectivity verification#16040
Merged
Enhance NSP deployment test with resource connectivity verification#16040
Conversation
Contributor
|
🚀 Dogfood this PR with:
curl -fsSL https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 16040Or
iex "& { $(irm https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 16040" |
Contributor
|
🚀 Deployment tests starting on PR #16040... This will deploy to real Azure infrastructure. Results will be posted here when complete. |
…th local app - Add /api/verify-blobs and /api/verify-keyvault endpoints to Server Program.cs - verify-blobs: creates/reads/deletes a blob to verify Storage connectivity - verify-keyvault: lists secret properties to verify Key Vault connectivity (read-only, no Officer role needed) - Step 12 now verifies both HTTP endpoints and resource connectivity in one shell command - Reorder AppHost code: NSP first, then chain .WithNetworkSecurityPerimeter(nsp) inline on Storage/KeyVault Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
1a03a08 to
89298e7
Compare
Contributor
|
🚀 Deployment tests starting on PR #16040... This will deploy to real Azure infrastructure. Results will be posted here when complete. |
Contributor
|
❌ Deployment E2E Tests failed — 23 passed, 7 failed, 0 cancelled View test results and recordings
|
Contributor
|
🎬 CLI E2E Test Recordings — 56 recordings uploaded (commit View recordings
📹 Recordings uploaded automatically from CI run #24253217757 |
davidfowl
approved these changes
Apr 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Enhances the NSP deployment E2E test (added in #16027) to actually verify that the deployed app can connect to Azure Storage and Key Vault through the Network Security Perimeter.
Changes:
.WithNetworkSecurityPerimeter(nsp)inline (cleaner style)./api/verify-blobsand/api/verify-keyvaultendpoints to the Server'sProgram.cs. These endpoints create, read, and delete resources to confirm real connectivity.This ensures the test validates not just that the app deploys, but that the NSP allows the Container App to actually talk to the PaaS resources.
Checklist