跳到主要內容
擴音器圖示

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

2月 10, 2027 | 6:00 - 7:00 下午 (UTC) 國際標準時間

準備好開始使用 AI 和最新技術嗎? Microsoft Reactor 提供活動、訓練和社群資源,協助開發人員、企業家和初創公司建置 AI 技術等等。 加入我們!

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

2月 10, 2027 | 6:00 - 7:00 下午 (UTC) 國際標準時間

準備好開始使用 AI 和最新技術嗎? Microsoft Reactor 提供活動、訓練和社群資源,協助開發人員、企業家和初創公司建置 AI 技術等等。 加入我們!

返回

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

2月 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 管理辦法.

本頁面的一部分可能是機器翻譯或人工智能翻譯的.