Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Move remaining ACA infrastructure generation to Aspire.Hosting.Azure.AppContainers #7076

Open
davidfowl opened this issue Jan 13, 2025 · 0 comments
Open

Move remaining ACA infrastructure generation to Aspire.Hosting.Azure.AppContainers #7076

davidfowl opened this issue Jan 13, 2025 · 0 comments
Labels
area-integrations Issues pertaining to Aspire Integrations packages azure Issues associated specifically with scenarios tied to using Azure
Milestone
Backlog

Comments

@davidfowl
Copy link
Member

Today we generate bicep for each container app when PublishAsAzureContainerApp is called, but we still defer to azd to do the compute and networking infrastructure generation. We should move this to the same logic that allocates the container app resources. This allows the app host to mutate core infrastructure in C#.
@davidfowl davidfowl added area-integrations Issues pertaining to Aspire Integrations packages azure Issues associated specifically with scenarios tied to using Azure labels Jan 13, 2025
@davidfowl davidfowl added this to the Backlog milestone Jan 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area-integrations Issues pertaining to Aspire Integrations packages azure Issues associated specifically with scenarios tied to using Azure
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
1 participant
@davidfowl