Support for container app job #11302
Open
+951
−472
Conversation
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
|
🚀 Dogfood this PR with:
curl -fsSL https://raw.githubusercontent.com/dotnet/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 11302Or
iex "& { $(irm https://raw.githubusercontent.com/dotnet/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 11302" |
github-actions
bot
added
the
area-integrations
eerhardt
commented
Sep 10, 2025
This pull request introduces support for Azure Container App Jobs in addition to existing Azure Container Apps functionality. It achieves this by adding new extension methods, annotation types, and context classes, and by refactoring the container app context management to handle both app and job types more flexibly. Support for Azure Container App Jobs: Added new extension methods PublishAsAzureContainerAppJob<T> for both ContainerResource and ProjectResource to allow resources to be published as Azure Container App Jobs, using a new configuration annotation. [1] [2] Introduced the AzureContainerJobCustomizationAnnotation class, which enables custom configuration actions for Azure Container App Jobs. Refactoring and Infrastructure: Added a new abstract base class BaseContainerAppContext to encapsulate shared logic for both container apps and jobs, including environment variable, argument, and volume processing. Updated ContainerAppEnvironmentContext to store and manage BaseContainerAppContext instances rather than just ContainerAppContext, and to instantiate the correct context type (app or job) based on resource annotations. Fix dotnet#4366
There was a problem hiding this comment.
Pull Request Overview
This PR adds support for Azure Container App Jobs to the existing Aspire Azure Container Apps functionality. This enables scenarios where containers need to run as scheduled or manual jobs rather than continuously running services.
Key changes:
- Added new
PublishAsAzureContainerAppJobextension methods for both container and project resources - Introduced a new base class architecture to handle shared logic between container apps and jobs
- Added validation to prevent conflicting container app and job configurations on the same resource
Reviewed Changes
Copilot reviewed 10 out of 10 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| AzureContainerAppsTests.cs | Added comprehensive test coverage for container app job functionality |
| ContainerAppJobContext.cs | New context class for handling Azure Container App Job creation and configuration |
| ContainerAppEnvironmentContext.cs | Updated to support both app and job contexts with proper validation |
| ContainerAppContext.cs | Refactored to inherit from BaseContainerAppContext, removing duplicated code |
| BaseContainerAppContext.cs | New abstract base class containing shared logic for both apps and jobs |
| AzureContainerJobCustomizationAnnotation.cs | New annotation type for job customization |
| AzureContainerAppProjectExtensions.cs | Added PublishAsAzureContainerAppJob extension method for project resources |
| AzureContainerAppContainerExtensions.cs | Added PublishAsAzureContainerAppJob extension method for container resources |
Comments suppressed due to low confidence (1)
src/Aspire.Hosting.Azure.AppContainers/AzureContainerAppProjectExtensions.cs:1
- Missing closing angle bracket. Should be
builder.AddProject<Projects.Api>().PublishAsAzureContainerAppJob
// Licensed to the .NET Foundation under one or more agreements.
eerhardt
commented
Sep 12, 2025
| /// </example> | ||
| /// </remarks> | ||
| [Experimental("ASPIREAZURE002", UrlFormat = "https://aka.ms/aspire/diagnostics/{0}")] | ||
| public static IResourceBuilder<T> PublishAsAzureContainerAppJob<T>(this IResourceBuilder<T> container, Action<AzureResourceInfrastructure, ContainerAppJob> configure) |
There was a problem hiding this comment.
@davidfowl - do I also need to do an extension method for Executables?
There was a problem hiding this comment.
eerhardt
added
the
azure
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
This pull request introduces support for Azure Container App Jobs in addition to existing Azure Container Apps functionality. It achieves this by adding new extension methods, annotation types, and context classes, and by refactoring the container app context management to handle both app and job types more flexibly.
Support for Azure Container App Jobs:
PublishAsAzureContainerAppJob<T>for bothContainerResourceandProjectResourceto allow resources to be published as Azure Container App Jobs, using a new configuration annotation. [1] [2]AzureContainerJobCustomizationAnnotationclass, which enables custom configuration actions for Azure Container App Jobs.Refactoring and Infrastructure:
BaseContainerAppContextto encapsulate shared logic for both container apps and jobs, including environment variable, argument, and volume processing.ContainerAppEnvironmentContextto store and manageBaseContainerAppContextinstances rather than justContainerAppContext, and to instantiate the correct context type (app or job) based on resource annotations.Fix #4366
Checklist
<remarks />and<code />elements on your triple slash comments?