devdeer.Templates.Bicep
24.0.12
See the version list below for details.
dotnet add package devdeer.Templates.Bicep --version 24.0.12
NuGet\Install-Package devdeer.Templates.Bicep -Version 24.0.12
<PackageReference Include="devdeer.Templates.Bicep" Version="24.0.12" />
<PackageVersion Include="devdeer.Templates.Bicep" Version="24.0.12" />
<PackageReference Include="devdeer.Templates.Bicep" />
paket add devdeer.Templates.Bicep --version 24.0.12
#r "nuget: devdeer.Templates.Bicep, 24.0.12"
#:package devdeer.Templates.Bicep@24.0.12
#addin nuget:?package=devdeer.Templates.Bicep&version=24.0.12
#tool nuget:?package=devdeer.Templates.Bicep&version=24.0.12
BICEP templates
Introduction
This is a collection of BICEP templates which serve as patterns for DEVDEER default resources in Azure. The folder modules contains the actual specific templates. BICEP files in this folder are meant to represent single resources in Azure. The folder components is providing BICEP modules which are creating resources which need different Azure deployments at one.
Developer notes
If you want to add another template just create a BICEP file in the root and add the modules needed. Afterwards create a JSON file named like the BICEP but ending with parameters.test.json. The just run the .\samples\deploy-test.ps1 providing the name of the folder.
The following pre-prequisites are needed on your machine:
Branching
2 branches are important for deploying the packages to Nuget:
main: Create a PR to this branch to deploy a new stable version.beta: Create a PR to this branch to deploy a new beta version. You don't need to add the "-beta". The pipelines will take care of that.
As soon as you created the PR a CI will run and then the CD will be triggered. The CD will ask for permission to deploy to Nuget. After approval the nuget push happens.
** Be aware that version handling is your responsibility! **
Learn more about Target Frameworks and .NET Standard.
-
net8.0
- No dependencies.
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 24.0.15 | 64 | 8/11/2026 |
| 24.0.13 | 143 | 8/6/2026 |
| 24.0.12 | 94 | 8/6/2026 |
| 24.0.11 | 158 | 8/4/2026 |
| 24.0.10 | 136 | 8/3/2026 |
| 24.0.8 | 133 | 7/30/2026 |
| 24.0.7 | 126 | 7/29/2026 |
| 24.0.6 | 127 | 7/29/2026 |
| 24.0.5 | 161 | 7/27/2026 |
| 24.0.4 | 226 | 7/22/2026 |
| 23.0.10 | 288 | 7/9/2026 |
| 23.0.8 | 176 | 7/7/2026 |
| 23.0.7 | 160 | 7/7/2026 |
| 23.0.6 | 204 | 7/3/2026 |
| 23.0.5 | 178 | 7/1/2026 |
| 23.0.3 | 224 | 6/27/2026 |
| 23.0.2 | 182 | 6/26/2026 |
| 23.0.1 | 165 | 6/26/2026 |
| 23.0.0 | 166 | 6/26/2026 |
| 22.0.0 | 259 | 6/19/2026 |
- BREAKING: App Gateway now is completely overhauled.
- BREAKING: App service outputs for managedIdentityId and userAssignedSlotManagedIdentityId are nullable now.
- BREAKING: Container app max replicas for scaling is changed from 10 to 1.
- New types for App Gateway deployment.
- Updated network resources to newer API version.
- App service has new optional userAssignedSlotManagedIdentityId parameter.
- Fixed an issue where parameter privateEndpointSettings.serviceConnectionGroupIds was disregarded in storageAccount.bicep module and was set to 'sqlServer'.
- VM component allows disabling of public IP, custom VM name and custom script URI.
- VNetGateway and VPN component now allow definition of additional routes for P2S.
- User assigned identity now exposes client id as an output.
- Fixed naming issue in Cosmos accounts.
- Cosmos db now by default configures Azure DNS if in a subnet.
- Blob service CORS now creates 1 entry for each origin.
- Fixed issue with private endpoints on deploy slots in Web Apps.
- VM component passes optional private static IP through.
-@secure()
output smbShares object = toObject(
azureFileShares ?? [],
share => toLower(share.shareName),
share => 'az${sep}file${sep}share${sep}${toLower(share.shareName)}'
)