Skip to content
/ integration-hub Public template

Sample template for deploying generic integration components using Azure Developer CLI (azd)

Notifications You must be signed in to change notification settings

marnixcox/integration-hub

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

7 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Integration Hub

template to deploy shared components for an integration platform

This template includes generic integration components like a shared Logic App Standard Plan, Azure Service Bus and Azure Artifacts.

It can be used together with one or more logicapp-standard-func implementations to implement an application integration platform.

Deploy

Application architecture

Deploy

This template utilizes the following Azure resources:

How to get started

  1. Install Visual Studio Code
  2. Create a new folder and switch to it in the Terminal tab
  3. Run azd auth login
  4. Run azd init -t https://github.com/marnixcox/integration-hub

Now the magic happens. The template contents will be downloaded into your project folder.

Contents

The following folder structure is created.

├── infra                      [ Infrastructure As Code files ]
│   ├── main.bicep             [ Main infrastructure file ]
│   ├── main.parameters.json   [ Parameters file ]
│   ├── avm                    [ Azure Verified Modules ]
│   └── core                   [ Full set of infra files provided by Azure Developer CLI team ]
├── scripts                    [ Scripts to package and publish NuGet packages ]
├── src                        [ Application code ]
│   ├── model                  [ NuGet package for (service bus) message definitions ]
│   └── library                [ NuGet package for useful code ]
└── azure.yaml                 [ Describes the app and type of Azure resources ]

Prerequisites

Azure Artifacts

First configure Azure Artifacts and create a feed. Enter the feed parameters in /scripts/nuget.ps1

$env:ORG_NAME $env:PROJECT_NAME $env:FEED_NAME

Provision Infrastructure

Let's first provision the infra components. Add a resourceToken parameter to the main.parameters.json to set the application name or leave it out to have a random name generated.

 "resourceToken": {
      "value": "appname"
    }
  • Run azd provision

First time an environment name, subscription and location need to be selected. These will then be stored in the .azure folder.

Select environment, subscription

Resource group and all components will be created.

Provision

Deployment pipelines

This template includes pipelines for a staged dev/tst/acc/prd deployment for a develop and main branch. Make sure to update the serviceConnection and AZURE_SUBSCRIPTION_ID accordingly.

Deployment

About

Sample template for deploying generic integration components using Azure Developer CLI (azd)

Topics

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages