Skip to content

docs(openapi): add APP Key exposure response steps - #1051

Closed
alick-liming wants to merge 1 commit into
feat/github-secret-scanning-docsfrom
docs/app-key-leak-remediation
Closed

alick-liming wants to merge 1 commit into
feat/github-secret-scanning-docsfrom
docs/app-key-leak-remediation

Conversation

@alick-liming

Copy link
Copy Markdown
Contributor

为 GitHub Secret Scanning 合作计划申请表单中的 Public Remediation Documentation 字段准备公开处置文档。

在 zh/openapi/introduction.mdx 和 en/openapi/introduction.mdx 的认证方式一节各新增一个小节:

  • APP Key 泄露了怎么办 / What to do if an APP Key is exposed:创建替代密钥 → 切换集成 → 删除或禁用旧 Key 的三步处置流程
  • 附 Note:如收到 Flashduty 密钥泄露通知邮件,按步骤尽快轮换(条件句式,功能未上线前也成立)

未改动 docs.json 导航(在现有页面内新增小节)。本地无 mint,未跑 broken-links;新增内容只引用了同页已有的 console 链接。

上线后公开 URL:

@ysyneu

ysyneu commented Oct 17, 2026

Copy link
Copy Markdown
Contributor

Superseded by #1070, which re-applies the still-relevant parts of this PR on current main (see the table there for what was ported and what was left out).

@ysyneu ysyneu closed this Oct 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants