Azure – Pauls Blog https://sterl.org Tue, 09 May 2023 08:06:35 +0000 de hourly 1 https://wordpress.org/?v=6.8.3 Azure Bicep CLI and functions cheet sheet https://sterl.org/2023/03/azure-bicep-cli-functions-cheet-sheet/ https://sterl.org/2023/03/azure-bicep-cli-functions-cheet-sheet/#respond Fri, 31 Mar 2023 15:06:05 +0000 https://sterl.org/?p=890 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 '<name of the subscription>'
Set-AzContext $context

Set default 

Set-AzDefault -ResourceGroupName <resource-group-name>

Run bicep deployment

New-AzResourceGroupDeployment -TemplateFile main.bicep

Read resource group

Get-AzResourceGroupDeployment -ResourceGroupName <resource-group-name> | 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

Links

]]> https://sterl.org/2023/03/azure-bicep-cli-functions-cheet-sheet/feed/ 0 Azure Node Functions Apps and OpenAPI Swagger https://sterl.org/2023/03/azure-node-functions-apps-and-openapi-swagger/ https://sterl.org/2023/03/azure-node-functions-apps-and-openapi-swagger/#respond Sun, 12 Mar 2023 09:15:26 +0000 https://sterl.org/?p=875 Sometimes we face the problem that we want to host a very simple web-service including a swagger-ui / OpenApi-UI. The question now is, what is the simplest solution, which works everywhere, even in a azure function app?

Where are of course some libs etc. which on the other hand require us to run the web-server. If we look into the doc using the simple unpkg HTML files looks like to be the simplest solution.

<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="utf-8" />
  <meta name="viewport" content="width=device-width, initial-scale=1" />
  <meta
    name="description"
    content="SwaggerUI"
  />
  <title>SwaggerUI</title>
  <link rel="stylesheet" href="https://unpkg.com/swagger-ui-dist@4.5.0/swagger-ui.css" />
</head>
<body>
<div id="swagger-ui"></div>
<script src="https://unpkg.com/swagger-ui-dist@4.5.0/swagger-ui-bundle.js" crossorigin></script>
<script>
  window.onload = () => {
    window.ui = SwaggerUIBundle({
      url: 'https://petstore3.swagger.io/api/v3/openapi.json',
      dom_id: '#swagger-ui',
    });
  };
</script>
</body>
</html>

What needs to be done

  • Get the HTML OpenAPI HTML file
  • Provide an OpenAPI YML or JSON
  • Create an endpoint which should host the doc

This solution works also for a spring web app or a AWS function. We will go ahead and look into a Node JavaScript example to see how it may look like:

Which means we have to create a new azure function endpoint where we want to host the OpenApi-UI:

function.json

We can set the function to „anonymous“ if we like and only get is required:

{
  "bindings": [
    {
      "authLevel": "anonymous",
      "type": "httpTrigger",
      "direction": "in",
      "name": "req",
      "methods": [
        "get"
      ]
    },
    {
      "type": "http",
      "direction": "out",
      "name": "res"
    }
  ]
}

openApi.html

The only adjustment to the original HTML file is the source of the yml or json file. You could also adjust the JS and CSS url:

<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="utf-8" />
  <meta name="viewport" content="width=device-width, initial-scale=1" />
  <meta name="description" content="My SwaggerUI" />
  <title>SwaggerUI</title>
  <link rel="stylesheet" href="https://unpkg.com/swagger-ui-dist@4.5.0/swagger-ui.css" />
</head>
<body>
<div id="swagger-ui"></div>
<script src="https://unpkg.com/swagger-ui-dist@4.5.0/swagger-ui-bundle.js" crossorigin></script>
<script>
  window.onload = () => {
    window.ui = SwaggerUIBundle({
      url: './doc?file=openApi.yml',
      dom_id: '#swagger-ui',
    });
  };
</script>
</body>
</html>

openApi.yml

Just as an example here. Note here the URL which has a funny value of _server.url_, we will replace this value later.

openapi: 3.0.2
info:
  title: My OpenAPI
  version: v1
servers:
  - url: "_server.url_"
paths:
  /foo:
    get:
      summary: Som cool function
      responses:
        '200':
          description: Retrieved entities
          content:
            application/json:
              schema:
                type: string

index.js

"use strict";
const fs = require('fs');
const util = require('util');
const readFileAsync = util.promisify(fs.readFile);

module.exports = async function (context, req) {
    switch(req.query.file) {
        case 'openApi.yml':
            // get the url and remove the doc suffix, azure specific
            const url = req.headers.referer.replace('/doc', '');
            let yml = await readFileAsync('doc/openApi.yml', 'UTF-8');
            yml = yml.replace('_server.url_', url);
            context.res = {
                body: yml,
                headers: {
                    "Content-Type": "application/yml; charset=utf-8"
                }
            };
            break;
        default:
            context.res = {
                body: await readFileAsync('doc/openApi.html', 'UTF-8'),
                headers: {
                    "Cache-Control": "max-age=600", // optional cache header
                    "Content-Type": "text/html; charset=utf-8"
                }
            };
            break;
    }
}

The switch case is where to ensure we load only files we want to publish, as so you have to extend the case block if you want to host the JS files too. Of course they have to be added to your directory.

Links

]]> https://sterl.org/2023/03/azure-node-functions-apps-and-openapi-swagger/feed/ 0 Azure DevOps Function App Deployment „No package found“ https://sterl.org/2023/03/azure-devops-function-app-deployment-no-package-found/ https://sterl.org/2023/03/azure-devops-function-app-deployment-no-package-found/#comments Fri, 10 Mar 2023 11:06:46 +0000 https://sterl.org/?p=863 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:

  1. build
  2. publish -> ArchiveFiles & PublishBuildArtifacts
  3. download an artefact -> DownloadBuildArtifacts
  4. 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: '<azure-subscription-name>'
  appName: '<azure-function-app-name>'

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: '<Resource Group Name>'
    #slotName: '<Slot name>'

Links

]]> https://sterl.org/2023/03/azure-devops-function-app-deployment-no-package-found/feed/ 2