知识卡片
应急流程应成为默认
日常交付若太慢,紧急修复时人就会绕过它;单设放松控制的应急流程又增加失误与不合规风险。应设计满足治理要求的最精简可靠流程,并把它用于每天工作,使同一条经过反复验证的路径也能足够快地修复生产。速度是守住流程的条件之一。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
- · 第21章 治理
原书出处 · 1 处
- 治理 · 查看原书依据
The normal workflow for delivering changes to production should be fast enough to get a fix through in an emergency. If the pipeline takes too long, people will be tempted to bypass it to make fixes manually, which often leads to mistakes. Even having a
参考来源
- 位置:《Infrastructure As Code》第21章《治理》(来源项目:book-sources;源文件:extracted/Infrastructure As Code/_epub-src/OEBPS/ch21.html)
- 结论依据:原文在该段定义概念并解释相关过程或限制,支撑“日常交付若太慢,紧急修复时人就会绕过它;单设放松控制的应急流程又增加失误与不合规风险”这一核心结论;正文的用途与边界据同小节后续论述整理。
- 原始内容:The normal workflow for delivering changes to production should be fast enough to get a fix through in an emergency. If the pipeline takes too long, people will be tempted to bypass it to make fixes manually, which often leads to mistakes. Even having a