Content for Aspire v13

.openpublishing.redirection.json

@@ -335,6 +335,10 @@
     {
       "source_path_from_root": "/docs/fundamentals/build-container-images.md",
       "redirect_url": "/dotnet/aspire/fundamentals/custom-deployments"
+    },
+    {
+      "source_path_from_root": "/docs/deployment/aspire-deploy/local-deployment-state.md",
+      "redirect_url": "/dotnet/aspire/deployment/deployment-state-caching"
     }
   ]
 }

docs/app-host/certificate-trust.md

@@ -0,0 +1,281 @@
+---
+title: Certificate trust customization in Aspire
+description: Learn how to customize trusted certificates for Executable and Container resources in Aspire to enable secure communication.
+ms.date: 11/10/2025
+ai-usage: ai-assisted
+---
+
+# Certificate trust customization in Aspire
+
+In Aspire, you can customize which certificates resources consider trusted for TLS/HTTPS traffic. This is particularly useful for resources that don't use the system's root trusted certificates by default, such as containerized applications, Python apps, and Node.js apps. By configuring certificate trust, you enable these resources to communicate securely with services that use certificates they wouldn't otherwise trust, including the Aspire dashboard's OTLP endpoint.
+
+> [!IMPORTANT]
+> Certificate trust customization only applies at run time. Custom certificates aren't included in publish or deployment artifacts.
+
+## When to use certificate trust customization
+
+Certificate trust customization is valuable when:
+
+- Resources need to trust the ASP.NET Core Development Certificate for local HTTPS communication.
+- Containerized services must communicate with the dashboard over HTTPS.
+- Python or Node.js applications need to trust custom certificate authorities.
+- You're working with services that have specific certificate trust requirements.
+- Resources need to establish secure telemetry connections to the Aspire dashboard.
+
+## Development certificate trust
+
+By default, Aspire attempts to add trust for the ASP.NET Core Development Certificate to resources that wouldn't otherwise trust it. This enables resources to communicate with the dashboard OTEL collector endpoint over HTTPS and any other HTTPS endpoints secured by the development certificate.
+
+You can control this behavior at the per-resource level using the `WithDeveloperCertificateTrust` API or through AppHost configuration settings.
+
+### Configure development certificate trust per resource
+
+To explicitly enable or disable development certificate trust for a specific resource:
+
+```csharp
+var builder = DistributedApplication.CreateBuilder(args);
+
+// Explicitly enable development certificate trust
+var nodeApp = builder.AddNpmApp("frontend", "../frontend")
+    .WithDeveloperCertificateTrust(trust: true);
+
+// Disable development certificate trust
+var pythonApp = builder.AddPythonApp("api", "../api", "main.py")
+    .WithDeveloperCertificateTrust(trust: false);
+
+builder.Build().Run();
+```
+
+## Certificate authority collections
+
+Certificate authority collections allow you to bundle custom certificates and make them available to resources. You create a collection using the `AddCertificateAuthorityCollection` method and then reference it from resources that need to trust those certificates.
+
+### Create and use a certificate authority collection
+
+```csharp
+using System.Security.Cryptography.X509Certificates;
+
+var builder = DistributedApplication.CreateBuilder(args);
+
+// Load your custom certificates
+var certificates = new X509Certificate2Collection();
+certificates.ImportFromPemFile("path/to/certificate.pem");
+
+// Create a certificate authority collection
+var certBundle = builder.AddCertificateAuthorityCollection("my-bundle")
+    .WithCertificates(certificates);
+
+// Apply the certificate bundle to resources
+builder.AddNpmApp("my-project", "../myapp")
+    .WithCertificateAuthorityCollection(certBundle);
+
+builder.Build().Run();
+```
+
+In the preceding example, the certificate bundle is created with custom certificates and then applied to a Node.js application, enabling it to trust those certificates.
+
+## Certificate trust scopes
+
+Certificate trust scopes control how custom certificates interact with a resource's default trusted certificates. Different scopes provide flexibility in managing certificate trust based on your application's requirements.
+
+The `WithCertificateTrustScope` API accepts a `CertificateTrustScope` value to specify the trust behavior.
+
+### Default trust scopes
+
+Different resource types have different default trust scopes:
+
+- **Append**: The default for most resources, appending custom certificates to the default trusted certificates.
+- **System**: The default for Python projects, which combines custom certificates with system root certificates because Python doesn't properly support Append mode.
+- **None**: The default for .NET projects on Windows, as there's no way to automatically change the default system store source.
+
+### Append mode
+
+Attempts to append the configured certificates to the default trusted certificates for a given resource. This mode is useful when you want to add trust for additional certificates while maintaining trust for the system's default certificates.
+
+```csharp
+var builder = DistributedApplication.CreateBuilder(args);
+
+builder.AddNodeApp("api", "../api")
+    .WithCertificateTrustScope(CertificateTrustScope.Append);
+
+builder.Build().Run();
+```
+
+> [!NOTE]
+> Not all languages and runtimes support Append mode. For example, Python doesn't natively support appending certificates to the default trust store.
+
+### Override mode
+
+Attempts to override a resource to only trust the configured certificates, replacing the default trusted certificates entirely. This mode is useful when you need strict control over which certificates are trusted.
+
+```csharp
+var builder = DistributedApplication.CreateBuilder(args);
+
+var certBundle = builder.AddCertificateAuthorityCollection("custom-certs")
+    .WithCertificates(myCertificates);
+
+builder.AddPythonModule("api", "./api", "uvicorn")
+    .WithCertificateAuthorityCollection(certBundle)
+    .WithCertificateTrustScope(CertificateTrustScope.Override);
+
+builder.Build().Run();
+```
+
+### System mode
+
+Attempts to combine the configured certificates with the default system root certificates and use them to override the default trusted certificates for a resource. This mode is intended to support Python or other languages that don't work well with Append mode.
+
+```csharp
+var builder = DistributedApplication.CreateBuilder(args);
+
+builder.AddPythonApp("worker", "../worker", "main.py")
+    .WithCertificateTrustScope(CertificateTrustScope.System);
+
+builder.Build().Run();
+```
+
+### None mode
+
+Disables all custom certificate trust for the resource, causing it to rely solely on its default certificate trust behavior.
+
+```csharp
+var builder = DistributedApplication.CreateBuilder(args);
+
+builder.AddContainer("service", "myimage")
+    .WithCertificateTrustScope(CertificateTrustScope.None);
+
+builder.Build().Run();
+```
+
+## Custom certificate trust configuration
+
+For advanced scenarios, you can specify custom certificate trust behavior using a callback API. This callback allows you to customize the command line arguments and environment variables required to configure certificate trust for different resource types.
+
+### Configure certificate trust with a callback
+
+Use `WithCertificateTrustConfiguration` to customize how certificate trust is configured for a resource:
+
+```csharp
+var builder = DistributedApplication.CreateBuilder(args);
+
+builder.AddContainer("api", "myimage")
+    .WithCertificateTrustConfiguration(async (ctx) =>
+    {
+        // Add a command line argument
+        ctx.Arguments.Add("--use-system-ca");
+
+        // Set environment variables with certificate paths
+        // CertificateBundlePath resolves to the path of the custom certificate bundle file
+        ctx.EnvironmentVariables["MY_CUSTOM_CERT_VAR"] = ctx.CertificateBundlePath;
+
+        // CertificateDirectoriesPath resolves to paths containing individual certificates
+        ctx.EnvironmentVariables["CERTS_DIR"] = ctx.CertificateDirectoriesPath;
+
+        await Task.CompletedTask;
+    });
+
+builder.Build().Run();
+```
+
+The callback receives a `CertificateTrustConfigurationCallbackAnnotationContext` that provides:
+
+- `Scope`: The `CertificateTrustScope` for the resource.
+- `Arguments`: Command line arguments for the resource. Values can be strings or path providers like `CertificateBundlePath` or `CertificateDirectoriesPath`.
+- `EnvironmentVariables`: Environment variables for configuring certificate trust. The dictionary key is the environment variable name; values can be strings or path providers. By default, includes `SSL_CERT_DIR` and may include `SSL_CERT_FILE` if Override or System scope is configured.
+- `CertificateBundlePath`: A value provider that resolves to the path of a custom certificate bundle file.
+- `CertificateDirectoriesPath`: A value provider that resolves to paths containing individual certificates.
+
+Default implementations are provided for Node.js, Python, and container resources. Container resources rely on standard OpenSSL configuration options, with default values that support the majority of common Linux distributions.
+
+### Configure container certificate paths
+
+For container resources, you can customize where certificates are stored and accessed using `WithContainerCertificatePaths`:
+
+```csharp
+var builder = DistributedApplication.CreateBuilder(args);
+
+builder.AddContainer("api", "myimage")
+    .WithContainerCertificatePaths(
+        customCertificatesDestination: "/custom/certs/path",
+        defaultCertificateBundlePaths: ["/etc/ssl/certs/ca-certificates.crt"],
+        defaultCertificateDirectoryPaths: ["/etc/ssl/certs"]);
+
+builder.Build().Run();
+```
+
+The `WithContainerCertificatePaths` API accepts three optional parameters:
+
+- `customCertificatesDestination`: Overrides the base path in the container where custom certificate files are placed. If not set or set to `null`, the default path of `/usr/lib/ssl/aspire` is used.
+- `defaultCertificateBundlePaths`: Overrides the path(s) in the container where a default certificate authority bundle file is located. When the `CertificateTrustScope` is Override or System, the custom certificate bundle is additionally written to these paths. If not set or set to `null`, a set of default certificate paths for common Linux distributions is used.
+- `defaultCertificateDirectoryPaths`: Overrides the path(s) in the container where individual trusted certificate files are found. When the `CertificateTrustScope` is Append, these paths are concatenated with the path to the uploaded certificate artifacts. If not set or set to `null`, a set of default certificate paths for common Linux distributions is used.
+
+> [!NOTE]
+> All desired paths must be configured in a single call to `WithContainerCertificatePaths` as only the most recent call to the API is honored.
+
+## Common scenarios
+
+### Enable HTTPS telemetry to the dashboard
+
+By default, Aspire enables development certificate trust for resources, allowing them to send telemetry to the dashboard over HTTPS:
+
+```csharp
+var builder = DistributedApplication.CreateBuilder(args);
+
+// Development certificate trust is enabled by default
+var nodeApp = builder.AddNpmApp("frontend", "../frontend");
+var pythonApp = builder.AddPythonApp("api", "../api", "main.py");
+
+builder.Build().Run();
+```
+
+### Trust custom certificates in containers
+
+When working with containerized services that need to trust custom certificates:
+
+```csharp
+using System.Security.Cryptography.X509Certificates;
+
+var builder = DistributedApplication.CreateBuilder(args);
+
+// Load custom CA certificates
+var customCerts = new X509Certificate2Collection();
+customCerts.Import("corporate-ca.pem");
+
+var certBundle = builder.AddCertificateAuthorityCollection("corporate-certs")
+    .WithCertificates(customCerts);
+
+// Apply to container
+builder.AddContainer("service", "myservice:latest")
+    .WithCertificateAuthorityCollection(certBundle);
+
+builder.Build().Run();
+```
+
+### Disable certificate trust for Python apps
+
+Python projects use System mode by default. To disable certificate trust customization for a Python app:
+
+```csharp
+var builder = DistributedApplication.CreateBuilder(args);
+
+// Disable certificate trust for Python apps
+builder.AddPythonModule("api", "./api", "uvicorn")
+    .WithCertificateTrustScope(CertificateTrustScope.None);
+
+builder.Build().Run();
+```
+
+## Limitations
+
+Certificate trust customization has the following limitations:
+
+- Currently supported only in run mode, not in publish mode.
+- Not all languages and runtimes support all trust scope modes.
+- Python applications don't natively support Append mode.
+- Custom certificate trust requires appropriate runtime support within the resource.
+
+## See also
+
+- [Host external executables in Aspire](executable-resources.md)
+- [Add Dockerfiles to your .NET app model](withdockerfile.md)
+- [AppHost configuration](configuration.md)

docs/azureai/ai-integrations-compatibility-matrix.md

@@ -118,7 +118,8 @@ The [Aspire.Hosting.GitHub.Models](https://www.nuget.org/packages/Aspire.Hosting
 ```csharp
 var builder = DistributedApplication.CreateBuilder(args);
 
-var chat = builder.AddGitHubModel("chat", "openai/gpt-4o-mini");
+var model = GitHubModel.OpenAI.OpenAIGpt4oMini;
+var chat = builder.AddGitHubModel("chat", model);
 
 builder.AddProject<Projects.ExampleProject>()
        .WithReference(chat);

docs/azureai/azureai-foundry-integration.md

@@ -63,7 +63,8 @@ var builder = DistributedApplication.CreateBuilder(args);
 
 var foundry = builder.AddAzureAIFoundry("foundry");
 
-var chat = foundry.AddDeployment("chat", "Phi-4", "1", "Microsoft");
+var model = AIFoundryModel.Microsoft.Phi4;
+var chat = foundry.AddDeployment("chat", model);
 
 builder.AddProject<Projects.ExampleProject>()
        .WithReference(chat)
@@ -75,17 +76,18 @@ builder.AddProject<Projects.ExampleProject>()
 The preceding code:
 
 - Adds an Azure AI Foundry resource named `foundry`.
-- Adds an Azure AI Foundry deployment resource named `chat` with a model name of `Phi-4`. The model name must correspond to an [available model](/azure/ai-foundry/foundry-models/concepts/models) in the Azure AI Foundry service.
+- Adds an Azure AI Foundry deployment resource named `chat` using the <xref:Aspire.Hosting.Azure.AIFoundryModel> constant for Phi-4. The model must correspond to an [available model](/azure/ai-foundry/foundry-models/concepts/models) in the Azure AI Foundry service.
 
-> [!NOTE]
-> The `format` parameter of the `AddDeployment(...)` method can be found in the Azure AI Foundry portal in the details page of the model, right after the `Quick facts` text.
+> [!TIP]
+> Use the strongly-typed <xref:Aspire.Hosting.Azure.AIFoundryModel> constants to avoid typos and ensure you're using valid model identifiers. These constants are grouped by publisher (for example, `AIFoundryModel.Microsoft.Phi4`, `AIFoundryModel.OpenAI.Gpt4o`).
 
 ### Configure deployment properties
 
 You can customize deployment properties using the <xref:Aspire.Hosting.AzureAIFoundryExtensions.WithProperties*> method:
 
 ```csharp
-var chat = foundry.AddDeployment("chat", "Phi-4", "1", "Microsoft")
+var model = AIFoundryModel.Microsoft.Phi4;
+var chat = foundry.AddDeployment("chat", model)
                   .WithProperties(deployment =>
                   {
                       deployment.SkuName = "Standard";
@@ -131,7 +133,8 @@ var builder = DistributedApplication.CreateBuilder(args);
 var foundry = builder.AddAzureAIFoundry("foundry")
                      .RunAsFoundryLocal();
 
-var chat = foundry.AddDeployment("chat", "phi-3.5-mini", "1", "Microsoft");
+var model = AIFoundryModel.Local.Phi35Mini;
+var chat = foundry.AddDeployment("chat", model);
 
 builder.AddProject<Projects.ExampleProject>()
        .WithReference(chat)
@@ -144,6 +147,9 @@ When the AppHost starts up, the local foundry service is also started. This requ
 
 The <xref:Aspire.Hosting.AzureAIFoundryExtensions.RunAsFoundryLocal*> method configures the resource to run as an emulator. It downloads and loads the specified models locally. The method provides health checks for the local service and automatically manages the Foundry Local lifecycle.
 
+> [!TIP]
+> Use the strongly-typed `AIFoundryModel.Local` constants for local development models. These constants are specifically optimized for Foundry Local (for example, `AIFoundryModel.Local.Phi4Mini`, `AIFoundryModel.Local.DeepseekR17b`).
+
 ### Assign roles to resources
 
 You can assign specific roles to resources that need to access the Azure AI Foundry service. Use the <xref:Aspire.Hosting.AzureAIFoundryExtensions.WithRoleAssignments*> method:

docs/cli-reference/aspire-deploy.md

@@ -55,6 +55,14 @@ The following options are available:
 
 - [!INCLUDE [option-project](includes/option-project.md)]
 
+- **`-e, --environment`**
+
+  The deployment environment name. Defaults to `production`. Each environment maintains its own isolated deployment state file.
+
+- **`--clear-cache`**
+
+  Clears the cached deployment state for the specified environment before deploying. When used, the deployment prompts for all values but doesn't save them to cache.
+
 - **`-o, --output-path`**
 
   The output path for deployment artifacts. Defaults to a folder named _deploy_ in the current directory.
@@ -84,3 +92,25 @@ The following options are available:
   ```Command
   aspire deploy --project './projects/apphost/orchestration.AppHost.csproj' -- -fast
   ```
+
+- Deploy to a specific environment:
+
+  ```Command
+  aspire deploy --environment staging
+  ```
+
+- Clear cached deployment state and deploy:
+
+  ```Command
+  aspire deploy --clear-cache
+  ```
+
+- Clear cached deployment state for a specific environment:
+
+  ```Command
+  aspire deploy --environment staging --clear-cache
+  ```
+
+## See also
+
+- [Deployment state caching](../deployment/deployment-state-caching.md)