A naukri.com initiative
Samcogan
2w
116
Local Deploy with Bicep
- Microsoft introduced a new feature in Bicep 0.36.1 called 'Local Deploy' that allows running deployments without connecting to Azure.
- Local Deploy is an Experimental feature aimed at supporting extensions for deploying resources other than Azure resources.
- Extensions available include Microsoft Graph for Entra ID resources and a Kubernetes extension for Kubernetes resources.
- Community extensions like GitHub, Local (for local scripts), Http (for HTTP requests), and KeyVault data plane are also supported.
- Local Deploy enables running Bicep deployments without Azure API connectivity, particularly useful for extensions like Local.
- To enable Local Deploy, the BicepConfig file needs to be updated with the experimental feature section.
- Additional extensions like Local need to be enabled in the config file to use their functionality.
- Scripts can be run inline or from external files using Bicep.
- Bicep file and BicepParams file define the parameters and script resources for the deployment.
- To execute a local deployment, the bicep CLI should be used directly instead of the az deployment commands.
- The Bicep Extension for VS Code provides a deployment pane for running local deployments with a graphical interface.
- Local Deploy, although niche, is valuable for non-Azure deployments as it bypasses Azure connectivity, rate limits, and pre-flight checks.
Read Full Article
7 Likes
For uninterrupted reading, download the app