Azure / Azure/az-prototype

[Knowledge] container-app: ## Advisory Notes — Stage 1: Managed Identity - **[Stabilit...

Open
#78 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
41
Forks
10
PR merge metrics
No merged PRs in 30d

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 version `2023-01-31` for 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 version `2023-01-31` for 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:
1. **Description** (one-line summary)
2. **When to Use** (scenarios and selection criteria)
3. **POC Defaults** (default SKU, tier, configuration)
4. **Terraform Patterns** (azapi_resource with RBAC)
5. **Bicep Patterns** (ARM template resources)
6. **Application Code** (Python, C#, Node.js — where applicable)
7. **Common Pitfalls** (deployment failures, misconfigurations)
8. **Production Backlog Items** (what changes for production)

Contributor guide

No contributing guide indexed for this repository

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.

Assessment

Tech stack
azure, csharp, node.js, python, terraform
Domain
cloud, documentation, infrastructure
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
70/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.