Azure Bicep CLI and functions cheet sheet

Paul Sterl — Fri, 31 Mar 2023 15:06:05 +0000

Overall Azure bicep is the best repalcement for AWS CDK currently available (2023) and the recommended way to express infrastructure-as-code in the aure universe.

Bicep CLI

All command require azure CLI and PowerShell 7.x.x

Select subscription by name / set context

$context = Get-AzSubscription -SubscriptionName ''
Set-AzContext $context

Set default

Set-AzDefault -ResourceGroupName

Run bicep deployment

New-AzResourceGroupDeployment -TemplateFile main.bicep

Read resource group

Get-AzResourceGroupDeployment -ResourceGroupName  | Format-Table

List resource groups

Get-AzResourceGroup

Bicep functions

Random unique name uniqueString

param fooUniceName string = 'fooo${uniqueString('constant-seed-value')}'

Create resource group with bicep

targetScope = 'subscription'
param location string = deployment().location

resource rg 'Microsoft.Resources/resourceGroups@2022-09-01' = {
    name: 'myName'
    location: location
}

az deployment create --location westeurope  --template-file .\main.bicep

Azure DevOps Function App Deployment „No package found“

Paul Sterl — Fri, 10 Mar 2023 11:06:46 +0000

Problem

##[error]Error: No package found with specified pattern: /home/vsts/work/1/a/**/*.zip
Check if the package mentioned in the task is published as an artifact in the build or a previous stage and downloaded in the current job.

This error occurs using the default MS deployment example. Even if we have an uploaded artefact

Solution

The problem is, that we have a deployment step by default but the MS documentation is outdated and so is missing the download step:

- task: DownloadBuildArtifacts@1
  inputs:
    buildType: 'current'
    downloadType: 'single'
    artifactName: 'drop'
    itemPattern: '**/*.zip'
    downloadPath: '$(System.ArtifactsDirectory)'

As so we have to:

build
publish -> ArchiveFiles & PublishBuildArtifacts
download an artefact -> DownloadBuildArtifacts
deploy: before we can trigger the deploy AzureFunctionApp task.

Deploy Node Function App using Azure DevOps

The full build and deploy Azure DevOps scripts looks than like:

# Node.js
# Build a general Node.js project with npm.
# Add steps that analyze code, save build artifacts, deploy, and more:
# https://docs.microsoft.com/azure/devops/pipelines/languages/javascript
variables:
  # Azure service connection established during pipeline creation
  azureSubscription: ''
  appName: ''

trigger:
- master

pool:
  vmImage: ubuntu-latest

steps:
- task: NodeTool@0
  inputs:
    versionSpec: '16.x'
  displayName: 'Install Node.js'
- script: |
    if [ -f extensions.csproj ]
    then
        dotnet build extensions.csproj --output ./bin
    fi
    npm install 
    npm run build --if-present
    npm prune --production  
- task: ArchiveFiles@2
  displayName: "Archive files"
  inputs:
    rootFolderOrFile: "$(System.DefaultWorkingDirectory)"
    includeRootFolder: false
    archiveFile: "$(System.DefaultWorkingDirectory)/build$(Build.BuildId).zip"
- task: PublishBuildArtifacts@1
  inputs:
    PathtoPublish: '$(System.DefaultWorkingDirectory)/build$(Build.BuildId).zip'
    artifactName: 'drop'
- task: DownloadBuildArtifacts@1
  inputs:
    buildType: 'current'
    downloadType: 'single'
    artifactName: 'drop'
    itemPattern: '**/*.zip'
    downloadPath: '$(System.ArtifactsDirectory)'
- task: AzureFunctionApp@1
  inputs:
    azureSubscription: $(azureSubscription)
    appType: functionAppLinux # default is functionApp
    appName: $(appName)
    package: '$(System.DefaultWorkingDirectory)/**/*.zip'
    runtimeStack: 'NODE|16' # this is optional
    deploymentMethod: 'auto' # auto is default
    #Uncomment the next lines to deploy to a deployment slot
    #Note that deployment slots is not supported for Linux Dynamic SKU
    #deployToSlotOrASE: true
    #resourceGroupName: ''
    #slotName: ''

CI/CD DevOps – Pauls Blog