[Knowledge] container-app: ## Advisory Notes — Stage 1: Managed Identity - **[Stabilit...
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 70/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Quiet
- Domain
- cloud, documentation, infrastructure
Research direction
Create knowledge/services/container-app.md and start by reviewing the advisory notes and the required section list in the issue. Cover the eight requested sections, including Terraform, Bicep, and applicable Python, C#, and Node.js patterns. Done means the new file exists and documents managed identity usage, defaults, pitfalls, and production backlog items.
Written by the indexing model from the issue text.
Description
Knowledge Contribution
Type: New service
File: knowledge/services/container-app.md
Status: NEW FILE — this knowledge file does not exist yet and must be created
Context
Advisory Notes — Stage 1: Managed Identity
-
[Stability] The identity module uses API version
2023-07-31-preview; preview APIs may introduce breaking changes or be retired — consider pinning to the GA version2023-01-31for production deployments. -
[Security] Deployment outputs (client ID, principal ID) are written to a local JSON file with no access controls; in CI/CD pipelines, prefer storing these in a Key Vault or using deployment output references directly to avoid credent
Rationale
Advisory Notes — Stage 1: Managed Identity
-
[Stability] The identity module uses API version
2023-07-31-preview; preview APIs may introduce breaking changes or be retired — consider pinning to the GA version2023-01-31for production deployments. -
[Security] Deployment outputs (client ID, principal ID) are written to a local JSON file with no access controls; in CI/CD pipelines, prefer storing these in a Key Vault or using deployment output references directly to avoid credent
Content to Add
## Advisory Notes — Stage 1: Managed Identity
- **[Stability]** The identity module uses API version `2023-07-31-preview`; preview APIs may introduce breaking changes or be retired — consider pinning
Source
Build advisory review
Required Knowledge File Sections
The new knowledge file MUST include ALL of these sections:
- Description (one-line summary)
- When to Use (scenarios and selection criteria)
- POC Defaults (default SKU, tier, configuration)
- Terraform Patterns (azapi_resource with RBAC)
- Bicep Patterns (ARM template resources)
- Application Code (Python, C#, Node.js — where applicable)
- Common Pitfalls (deployment failures, misconfigurations)
- Production Backlog Items (what changes for production)
- Dominant language
- Python
- Stars
- 41
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Azure/az-prototype
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Azure/az-prototype#71 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 70/100
Azure/az-prototype#66 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
Azure/az-prototype#65 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Azure/az-prototype#64 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Azure/az-prototype#63 ·
All issues in Azure/az-prototype
Similar issues
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
simonw/sqlite-utils#872 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100