跳至主要内容
扩音器图标

GitHub Universe on the Road

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

Infrastructure as Code with Azure Bicep and Deployment Stacks

准备好开始使用 AI 和最新技术了吗? Microsoft Reactor 提供活动、培训和社区资源,帮助开发人员、企业家和初创公司利用 AI 技术等。 快加入我们吧!

Infrastructure as Code with Azure Bicep and Deployment Stacks

准备好开始使用 AI 和最新技术了吗? Microsoft Reactor 提供活动、培训和社区资源,帮助开发人员、企业家和初创公司利用 AI 技术等。 快加入我们吧!

返回

Infrastructure as Code with Azure Bicep and Deployment Stacks

  • 形式:
  • alt##Livestream直播

主题: 基础设施

语言: 英语

  • 此系列中的活动:
  • 3

A three-part live demo series from the Azure Bicep product team on building, governing, and scaling Azure infrastructure as code.

Episode 1 covers Bicep fundamentals in VS Code with Azure Verified Modules, deployment stacks, and Stacks What-If.

Episode 2 covers managing environment lifecycles, finding portal drift with Stacks What-If, and blocking unauthorized changes with deny settings.

Episode 3 shows how to scale Bicep across teams and environments with modules, a private registry, typed parameters, linter rules, GitHub Copilot, and GitHub Actions.

即将举办的活动

单击下面的活动以了解详细信息并注册各个活动。

所有时间采用 - 协调世界时

1月

13

星期三

2027

Bicep 101: Learning the Fundamentals of Microsoft's Infrastructure as Code Language

6:00 下午 - 7:00 下午 (UTC)

Teams that manage Azure through the portal or with scripts often cannot repeat a deployment exactly or review a change before it happens. This session teaches the fundamentals of Bicep to people who are new to infrastructure as code. I am a product manager at Microsoft on Azure Bicep and owning Deployment Stacks. Bicep is Azure's native infrastructure as code language, and it is stateless, so there is no state file to manage. In the demo I write a Bicep file in VS Code, use IntelliSense and the linter to catch mistakes as I type, and deploy it with the Azure CLI. I then use Azure Verified Modules, which provide ready-made Bicep modules for common resources, and deploy the environment as a deployment stack, which manages a group of resources as a single unit. Before each change, Stacks What-If shows exactly which resources will be created, modified, or deleted, and deny settings block deletes made outside the stack. The result is a first Bicep deployment you can repeat, review, and build on. Everything runs live from VS Code and the Azure CLI. What attendees will learn: - How to write and deploy a Bicep file in VS Code with the Azure CLI. - How Azure Verified Modules provide ready-made Bicep modules for common resources. - How a deployment stack and Stacks What-If let you see and control every change to an environment. [eventID:27814]

  • 形式:
  • alt##Livestream直播

主题: 基础设施

语言: 英语

详细信息

1月

27

星期三

2027

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

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: 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]

  • 形式:
  • alt##Livestream直播

主题: 基础设施

语言: 英语

详细信息

2月

10

星期三

2027

Bicep 102: Beyond the Basics, Scaling Your Infrastructure as Code with Bicep

6:00 下午 - 7:00 下午 (UTC)

One Bicep file works well for one team and one environment, but it gets hard to share, review, and keep consistent once several teams and environments depend on it. This session picks up where Bicep 101 ends and shows how to scale a Bicep codebase. 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. In the demo I split a single Bicep file into modules, replace hand-written resources with Azure Verified Modules, and publish a shared module to a private registry so other teams use the same version. I add a parameters file for each environment and user-defined types, so a wrong value fails before anything is deployed, and set linter rules for the whole repository in bicepconfig.json. I then use GitHub Copilot to bring resources that were built by hand into the same code and add a GitHub Actions pipeline that runs Stacks What-If before every deployment, which confirms that adopting those resources changes nothing in Azure. The result is Bicep code that many teams can share and deploy the same way. Everything runs live from VS Code, GitHub, and the Azure CLI. What attendees will learn: How to structure Bicep with modules, Azure Verified Modules, and a private registry that several teams can share. How to keep environments consistent with parameters files, user-defined types, and linter rules. How to bring hand-built resources into code with GitHub Copilot and check every deployment with Stacks What-If. [eventID:27836]

  • 形式:
  • alt##Livestream直播

主题: 基础设施

语言: 英语

详细信息

主讲人

本页面的部分内容可能是机器翻译或人工智能翻译.