chore(management-portal): remove DAB from infra, drop Aspire AppHost runtime, and ignore build outputs

Author: srnichols

management-portal/AppHost/AppHost.csproj

@@ -4,12 +4,10 @@
     <TargetFramework>net9.0</TargetFramework>
     <ImplicitUsings>enable</ImplicitUsings>
     <Nullable>enable</Nullable>
-  <IsAspireAppHost>true</IsAspireAppHost>
   </PropertyGroup>
   <ItemGroup>
     <ProjectReference Include="..\src\Portal\Portal.csproj" />
   </ItemGroup>
   <ItemGroup>
-    <PackageReference Include="Aspire.Hosting.AppHost" Version="9.4.1" />
   </ItemGroup>
 </Project>

management-portal/AppHost/Program.cs

@@ -1,42 +1,11 @@
-using Aspire.Hosting;
+using System;
 
-var builder = DistributedApplication.CreateBuilder(args);
+// Minimal AppHost shim.
+// This project previously used the .NET Aspire AppHost runtime. That runtime and automatic DAB startup
+// have been removed. To run the portal locally, run the Portal project directly.
 
-// Make containerized resources optional to avoid requiring DCP when running `dotnet run`.
-var skipContainersEnv = Environment.GetEnvironmentVariable("ASPIRE_SKIP_CONTAINERS");
-var skipContainers = string.IsNullOrWhiteSpace(skipContainersEnv) || bool.TryParse(skipContainersEnv, out var val) && val;
+Console.WriteLine("AppHost shim: Aspire AppHost usage removed.");
+Console.WriteLine("Run the Portal directly with: dotnet run --project ..\\src\\Portal\\Portal.csproj");
+Console.WriteLine("Or use the one-command local script: pwsh -File ..\\..\\scripts\\run-local.ps1");
 
-if (!skipContainers)
-{
-    // Cosmos DB Emulator (for local dev). If you prefer local emulator app, set COSMOS_CONNECTION_STRING externally and skip this container.
-    var cosmosEmu = builder.AddContainer("cosmos", "mcr.microsoft.com/cosmosdb/linux/azure-cosmos-emulator", tag: "latest")
-        .WithEnvironment("AZURE_COSMOS_EMULATOR_ENABLE_TELEMETRY", "false")
-        .WithEnvironment("AZURE_COSMOS_EMULATOR_PARTITION_COUNT", "3")
-        .WithEnvironment("AZURE_COSMOS_EMULATOR_ENABLE_DATA_PERSISTENCE", "true")
-        .WithContainerRuntimeArgs("--cap-add=NET_ADMIN")
-        .WithHttpEndpoint(port: 8085, targetPort: 8081, name: "cosmos"); // maps emulator 8081 -> 8085 on host
-
-    // Connection strings:
-    // - Inside containers (same Docker/Aspire network): use the container hostname `cosmos` at port 8081.
-    // - From the host (for local tools like the Seeder): use https://localhost:8085 mapped above.
-    var cosmosConnForContainers = "AccountEndpoint=https://cosmos:8081/;AccountKey=C2y6yDjf5/R+ob0N8A7Cgv30VRDJIWEHLM+4QDU5DE2nQ9nDuVTqobD4b8mGGyPMbIZnqyMsEcaGQy67XIw/Jw==;";
-    var cosmosConnForHost = "AccountEndpoint=https://localhost:8085/;AccountKey=C2y6yDjf5/R+ob0N8A7Cgv30VRDJIWEHLM+4QDU5DE2nQ9nDuVTqobD4b8mGGyPMbIZnqyMsEcaGQy67XIw/Jw==;";
-
-    var dab = builder.AddContainer("dab", "mcr.microsoft.com/data-api-builder", tag: "latest")
-        .WithBindMount("..\\dab\\dab-config.json", "/App/dab-config.json")
-        .WithEnvironment("ASPNETCORE_URLS", "http://+:8082")
-        // Prefer an explicit COSMOS_CONNECTION_STRING if provided by the user, otherwise default to the container-network connection.
-        .WithEnvironment("COSMOS_CONNECTION_STRING", Environment.GetEnvironmentVariable("COSMOS_CONNECTION_STRING") ?? cosmosConnForContainers)
-        // Provide COSMOS_CONNECTION_STRING via environment or user-secrets for DAB to connect to Cosmos
-        .WithHttpEndpoint(port: 8082, name: "http")
-        .WithArgs(["dab", "start", "--host", "0.0.0.0", "--config", "/App/dab-config.json"]);
-}
-
-// (Optional) Run Seeder manually: dotnet run --project management-portal/Seeder 
-
-var portal = builder.AddProject("portal", "..\\src\\Portal\\Portal.csproj")
-    .WithEnvironment("ASPNETCORE_URLS", "http://+:8081")
-    .WithEnvironment("DAB_GRAPHQL_URL", "http://localhost:8082/graphql")
-    .WithHttpEndpoint(port: 8081, name: "http");
-
-builder.Build().Run();
+return 0;

management-portal/Aspire/ServiceDefaults/Extensions.cs

@@ -28,25 +28,17 @@ For detailed authentication setup, see the main documentation: [DEPLOYMENT_GUIDE
 - GraphQL: <http://localhost:8082/graphql>
 - Cosmos Emulator: <https://localhost:8085>
 
-## Local Run (AppHost)
+Local Run (AppHost)
 
 - Build AppHost: dotnet build management-portal/AppHost
 - Run AppHost: dotnet run --project management-portal/AppHost
 - Portal URL: <http://localhost:8081>
 
-Prereqs for Aspire run (CLI)
-
-- .NET 9 SDK installed (9.0.4xx or newer)
-- .NET Aspire 9 workload and tools installed
- 	- dotnet workload install aspire
- 	- Ensure Aspire Hosting SDK pack is 9.x under C:\Program Files\dotnet\packs\Aspire.Hosting.Sdk
- 	- Install Aspire Distributed Control Plane (DCP) and Aspire Dashboard (via Visual Studio Installer > Individual components > .NET Aspire 9)
-- CLI: aspire --version should show 9.x
+Note: AppHost is no longer dependent on the .NET Aspire runtime for local runs. The portal hosts a built-in Hot Chocolate GraphQL endpoint and local scripts now rely on that endpoint.
 
 Troubleshooting
 
-- If aspire run says "not an Aspire app host project" or AppHost complains about missing DCP/Dashboard, install the Aspire 9 SDK pack and DCP/Dashboard as above.
-- Use the one-command local scripts as a fallback while you set up Aspire.
+- If you encounter issues running the portal locally, use the one-command local scripts `pwsh -File .\scripts\run-local.ps1` and `pwsh -File .\scripts\stop-local.ps1` which no longer start DAB automatically.
 
 ## Config
 

management-portal/Aspire/ServiceDefaults/ServiceDefaults.csproj

@@ -12,31 +12,16 @@ spec:
         duration: 2s
         maxRetries: 3
         maxInterval: 30s
-      dab-service-retry:
-        policy: linear
-        duration: 1s
-        maxRetries: 5
-        maxInterval: 10s
     circuitBreakers:
       azure-api-cb:
         maxRequests: 5
         timeout: 30s
         trip: consecutiveFailures >= 3
         resetInterval: 60s
-      dab-service-cb:
-        maxRequests: 10
-        timeout: 15s
-        trip: consecutiveFailures >= 5
-        resetInterval: 30s
     timeouts:
       azure-api-timeout: 45s
-      dab-service-timeout: 20s
   targets:
     apps:
-      dab:
-        retry: dab-service-retry
-        circuitBreaker: dab-service-cb
-        timeout: dab-service-timeout
     components:
       cache-store:
         retry: azure-api-retry