知识卡片
脚本编排可替换依赖
部署脚本可以先查询提供者输出,再把值传给消费者,同一栈在生产和测试可采用不同发现模式。按场景拆分脚本或模块化,避免把所有栈实现细节塞进一个巨型脚本。可替换入口的价值是独立执行和测试,而不只是减少栈代码行数。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 集成基础设施栈 · 查看原书依据
A stack deployment script can implement any of the resource discovery patterns described in this chapter. It can even implement different patterns for different contexts, such as when deploying the stack to a local emulator, or in a test suite where it may provide a stripped-down version of the needed resources. See “Use Test Fixtures
参考来源
- 位置:《Infrastructure As Code》第9章《集成基础设施栈》(来源项目:book-sources;源文件:extracted/Infrastructure As Code/_epub-src/OEBPS/ch09.html)
- 结论依据:原文说明部署脚本可以先查询提供者输出,再把值传给消费者,同一栈在生产和测试可采用不同发现模式;本卡据此解释其用途及适用边界。
- 原始内容:A stack deployment script can implement any of the resource discovery patterns described in this chapter. It can even implement different patterns for different contexts, such as when deploying the stack to a local emulator, or in a test suite where it may provide a stripped-down version of the needed resources. See “Use Test Fixtures