devdeer.Templates.Bicep 6.0.10

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 deployments are taking there options from the DEVDEER AKV from the key SpockBicepSettings. This gets downloaded and stored in ./bicepSettings.json. After one deployment this file is restored using a tmp.json which lives only for the runtime of the deployment and gets deleted automatically afterwards.

The following pre-prequisites are needed on your machine:

• Bicep CLI
• nuget CLI
• DEVDEER CAF

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! **