Skip to content

Bicep module repository; this contains Bicep modules that are published to an ACR for use in many projects. Bicep modules are pushed to ACR with an Azure DevOps pipeline.

License

Notifications You must be signed in to change notification settings

frasermolyneux/bicep-modules

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Bicep Modules

Stage Status
DevOps Secure Scanning Build Status
Build Build Status
Release to Production Build Status

Overview

This repository contains common Bicep modules and associated Azure DevOps pipelines for the validation and deployment of them to an Azure Container Registry.

The Azure Container Registry is deployed by the platform-strategic-services project and therefore a dependency.


Related Projects


Solution

The included Bicep modules have been extracted out of a series of projects that I have worked on through my learning and development. They are largely focused on Azure Integration Services such as API Management, Azure Functions, App Services and Key Vault.

Versioning

Each module within the solution has a metadata .json file that is within the metadata folder. Currently this contains a JSON payload that simply has a version object containing major, minor and revision properties - there is the future potential to add additional metadata here such as tagging, author and description. For each module file there must be a metadata file and for a new version to be pushed the metadata file must be updated.

If the build is running from any branch other than main then a -preview suffix is added to the tag and the .x and latest tags will not be pushed.

As such, for a new version to be pushed the metadata file is required to be updated. There is no automation at present as it is not warranted.


Pipelines

The one-pipeline is within the .azure-pipelines folder and output is visible on the frasermolyneux/Personal-Public Azure DevOps project.

The Publish-BicepModuleToAcr.ps1 script is executed per module and uses the following rules to publish:

  • Will only push a new version if the major.minor.revision tag does not already exist
  • When pushing a new version will also push that version using the a .x and latest tag

Contributing

Please read the contributing guidance; this is a learning and development project.


Security

Please read the security guidance; I am always open to security feedback through email or opening an issue.

About

Bicep module repository; this contains Bicep modules that are published to an ACR for use in many projects. Bicep modules are pushed to ACR with an Azure DevOps pipeline.

Topics

Resources

License

Security policy

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published