Document AZD's strategies for Azure Container Apps #5216
+121
−0
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 PR adds documentation for the strategies Azure Developer CLI (AZD) uses for provisioning and deploying Azure Container Apps:
container-app-upsert
: A Bicep-based approach for creating or updating existing Azure Container Appsdelay-deployment
: A strategy used by .NET Aspire applications that delays full container app configuration until deployment timeThe new documentation file (
cli/azd/docs/container-app-strategies.md
) includes:This documentation will be helpful for both customers implementing these strategies and AI models that need to understand the steps to implement them.
Changes
cli/azd/docs/container-app-strategies.md
Fixes #5195.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.