Torrey Trahanovsky
Microsoft
enero 27, 2027 | 6:00 - 7:00 p. m. (UTC) Hora universal coordinada
¿Está listo para empezar a trabajar con la inteligencia artificial y las tecnologías más recientes? Microsoft Reactor proporciona eventos, formación y recursos comunitarios para ayudar a los desarrolladores, empresarios y startups a basarse en la tecnología de inteligencia artificial y mucho más. ¡Acompáñenos!
enero 27, 2027 | 6:00 - 7:00 p. m. (UTC) Hora universal coordinada
¿Está listo para empezar a trabajar con la inteligencia artificial y las tecnologías más recientes? Microsoft Reactor proporciona eventos, formación y recursos comunitarios para ayudar a los desarrolladores, empresarios y startups a basarse en la tecnología de inteligencia artificial y mucho más. ¡Acompáñenos!
enero 27, 2027 | 6:00 - 7:00 p. m. (UTC) Hora universal coordinada
tema del evento: Infraestructura
Idioma: Inglés
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]
Oradores
¿Ya está registrado y necesita cancelar su registro? Cancelar registro
Este evento forma parte de Infrastructure as Code with Azure Bicep and Deployment Stacks Series.
Haga clic aquí para visitar la página de series donde pueden verse todos los eventos próximos y a petición.