返回主题:基础设施即代码与编排

知识卡片

普通读书笔记卡 · 1903.c.9.c

状态锁不防版本覆盖

理解等级:高级

状态锁能防两次部署同时执行,却不能防开发者按顺序把彼此不兼容的本地版本应用到同一实例。因此共享环境仍可能来回丢配置。个人开发应使用个人实例;多人使用的实例应从共享仓库经中心服务部署,使变更能先发现、合并并留轨迹。

这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • 部署基础设施 · 查看原书依据

      Note that a locking solution, such as Terraform’s state locking, won’t prevent this situation. Locking stops two people from applying their code to the same instance simultaneously. But, as of this writing, locking solutions don’t stop people from applying their own, conflicting versions of code

    参考来源

    - 位置:《Infrastructure As Code》第19章《部署基础设施》(来源项目:book-sources;源文件:extracted/Infrastructure As Code/_epub-src/OEBPS/ch19.html) - 结论依据:原文在该段定义概念并解释相关过程或限制,支撑“状态锁能防两次部署同时执行,却不能防开发者按顺序把彼此不兼容的本地版本应用到同一实例”这一核心结论;正文的用途与边界据同小节后续论述整理。 - 原始内容:Note that a locking solution, such as Terraform’s state locking, won’t prevent this situation. Locking stops two people from applying their code to the same instance simultaneously. But, as of this writing, locking solutions don’t stop people from applying their own, conflicting versions of code