Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

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

未关闭
#73 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
55/100
Issue 类型
文档
描述清晰度
基本清楚
活跃度
冷清
技术栈
azure, csharp, node.js, python, terraform

调研方向

创建 knowledge/services/web-app.md,并首先审阅 Managed Identity advisory notes 和列出的源,包括 API 版本和部署输出方面的注意事项。将文件组织为全部八个必需部分,涵盖带 RBAC 的 Terraform azapi_resource、Bicep 模式,以及适用的 Python、C# 和 Node.js 示例。完成的标准是每个必需部分都已存在,并且已记录所述的 POC 和生产环境指导。

由索引模型根据 Issue 内容生成。

描述

Knowledge Contribution

Type: New service
File: knowledge/services/web-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)
主要语言
Python
星标
41
派生
10
PR 合并指标
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

Azure/az-prototype 的其他 Issue

查看 Azure/az-prototype 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。