Torrey Trahanovsky
Microsoft
1月 27, 2027 | 6:00 - 7:00 下午 (UTC) 國際標準時間
準備好開始使用 AI 和最新技術嗎? Microsoft Reactor 提供活動、訓練和社群資源,協助開發人員、企業家和初創公司建置 AI 技術等等。 加入我們!
1月 27, 2027 | 6:00 - 7:00 下午 (UTC) 國際標準時間
準備好開始使用 AI 和最新技術嗎? Microsoft Reactor 提供活動、訓練和社群資源,協助開發人員、企業家和初創公司建置 AI 技術等等。 加入我們!
1月 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.
按一下這裡以 造訪系列頁面 您可以在其中查看所有即將推出和隨選活動。