Torrey Trahanovsky
Microsoft
一月 27, 2027 | 6:00 - 7:00 下午 (UTC) 协调世界时
准备好开始使用 AI 和最新技术了吗? Microsoft Reactor 提供活动、培训和社区资源,帮助开发人员、企业家和初创公司利用 AI 技术等。 快加入我们吧!
一月 27, 2027 | 6:00 - 7:00 下午 (UTC) 协调世界时
准备好开始使用 AI 和最新技术了吗? Microsoft Reactor 提供活动、培训和社区资源,帮助开发人员、企业家和初创公司利用 AI 技术等。 快加入我们吧!
一月 27, 2027 | 6:00 - 7:00 下午 (UTC) 协调世界时
主题: 基础设施
语言: 英语
Once an Azure environment is deployed, it rarely stays the way the code describes it: people change settings in the portal, delete resources by hand, and leave old resources running.
Deployment stacks are Azure's standard for managing infrastructure as code across that lifecycle, with drift detection and governance built in.
I am a product manager at Microsoft on Azure Bicep and owning Deployment Stacks. Bicep is Azure's native infrastructure as code language and a stateless alternative to Terraform, so there is no state file to store, secure, or keep in sync.
A deployment stack is a resource that manages a group of resources as a single unit across its lifecycle. In the demo I deploy an environment from Bicep as a deployment stack, then change a security rule and delete a resource in the portal. Stacks What-If with the same template lists those changes, and one more deployment puts the environment back. I then set deny settings so managed resources cannot be changed or deleted outside the stack, and choose whether resources removed from the template are detached or deleted.
When the environment is no longer needed, a single delete removes everything the stack manages. Everything runs live from the Azure CLI. The tools are Azure specific; the practices apply to any infrastructure as code workflow.
What attendees will learn:
[eventID:27816]
主讲人
已注册并且需要取消? 取消注册
此活动属于 Infrastructure as Code with Azure Bicep and Deployment Stacks Series.
单击此处 访问“系列”页 可在此处查看所有即将举办的活动和点播活动。