Lompati ke konten utama
ikon megafon

GitHub Universe on the Road

GitHub Universe is going on the road. Find a stop near you and join the experience.

Deployment Stacks: Azure's Standard for Infrastructure as Code, Drift Detection, and

Januari 27, 2027 | 6.00 - 7.00 PM (UTC) Waktu Universal Terkoordinasi

Siap untuk mulai menggunakan AI dan teknologi terbaru? Microsoft Reactor menyediakan acara, pelatihan, dan sumber daya komunitas untuk membantu pengembang, pengusaha, dan startup dibangun berdasarkan teknologi AI dan banyak lagi. Gabung dengan kami!

Deployment Stacks: Azure's Standard for Infrastructure as Code, Drift Detection, and

Januari 27, 2027 | 6.00 - 7.00 PM (UTC) Waktu Universal Terkoordinasi

Siap untuk mulai menggunakan AI dan teknologi terbaru? Microsoft Reactor menyediakan acara, pelatihan, dan sumber daya komunitas untuk membantu pengembang, pengusaha, dan startup dibangun berdasarkan teknologi AI dan banyak lagi. Gabung dengan kami!

Kembali

Deployment Stacks: Azure's Standard for Infrastructure as Code, Drift Detection, and

Januari 27, 2027 | 6.00 - 7.00 PM (UTC) Waktu Universal Terkoordinasi

  • Format:
  • alt##LivestreamStreaming Langsung

Topik: Infrastruktur

Bahasa: Inggris

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:

  • How a deployment stack manages an Azure environment as one unit, from the first deployment to the final delete.
  • How to find drift with Stacks What-If and bring the environment back to what the code describes.
  • How to govern changes with deny settings, and choose what happens to resources removed from the template.

[eventID:27816]

  • VS Code
  • Azure Bicep
  • Azure Deployment Stacks
  • Azure Verified Modules
  • Azure CLI

Pembicara

Sudah mendaftar dan perlu membatalkan? Batalkan pendaftaran

Pendaftaran

Masuk dengan Akun Microsoft Anda

Masuk

Atau masukkan alamat email Anda untuk mendaftar

*

Dengan mendaftar untuk acara ini, Anda setuju untuk mematuhi Kode Etik Microsoft Reactor.

Bagian dari halaman ini mungkin diterjemahkan oleh mesin atau AI.