From 090dc0d793b1bf62b28e8dcc9133b5f89819f11c Mon Sep 17 00:00:00 2001 From: "aspire-repo-bot[bot]" <268009190+aspire-repo-bot[bot]@users.noreply.github.com> Date: Thu, 8 Oct 2026 23:24:20 +0000 Subject: [PATCH] docs: remove obsolete ASPIREAZURE001 suppression from role-assignments example Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .../content/docs/integrations/cloud/azure/role-assignments.mdx | 2 -- 1 file changed, 2 deletions(-) diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/role-assignments.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/role-assignments.mdx index d6b1415887..2d75752696 100644 --- a/src/frontend/src/content/docs/integrations/cloud/azure/role-assignments.mdx +++ b/src/frontend/src/content/docs/integrations/cloud/azure/role-assignments.mdx @@ -114,8 +114,6 @@ Aspire represents each set of role assignments as an `AzureRoleAssignmentResourc The following example shows how to add a pipeline step that runs during `WellKnownPipelineSteps.BeforeStart` and enumerates all `AzureRoleAssignmentResource` instances that target a specific Azure resource: ```csharp title="AppHost.cs" -#pragma warning disable ASPIREAZURE001 // AzureEnvironmentResource is Experimental - var builder = DistributedApplication.CreateBuilder(args); var keyVault = builder.AddAzureKeyVault("vault");