跳至主要内容
扩音器图标

GitHub Universe on the Road

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

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

二月 10, 2027 | 6:00 - 7:00 下午 (UTC) 协调世界时

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

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

二月 10, 2027 | 6:00 - 7:00 下午 (UTC) 协调世界时

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

返回

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

二月 10, 2027 | 6:00 - 7:00 下午 (UTC) 协调世界时

  • 形式:
  • alt##Livestream直播

主题: 基础设施

语言: 英语

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]

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

主讲人

已注册并且需要取消? 取消注册

注册

使用 Microsoft 帐户登录

登录

或输入你的电子邮件地址进行注册

*

注册参加此活动即表示你同意遵守 Microsoft Reactor 行为准则.

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