Skip to content

Latest commit

 

History

History
38 lines (21 loc) · 1.91 KB

dashboard-migration.md

File metadata and controls

38 lines (21 loc) · 1.91 KB

home | dashboard | dashboard installation

Dashboard Migration Guide

This document will guide you through the process of migrating the build & release pipelines to the new procedure associated with version 4.7.0 or greater.

Build Pipeline

Remove Backend

Backend and Dashboard have now merged in one build, this means that Backend will no longer be used so this build pipeline can be safely deleted.

New Storage container

The storage container has been renamed from dashboardfrontend to dashboard, which means that you need to request a new SAS token and update the variable accordingly.

Next, navigate to the powershell task that pulls the resources from blob and change the StorageContainerName parameter value from dashboardfrontend to dashboard.

Apart from this new storage container, nothing changes for the build pipeline.

The difference lies in the artifacts that the build produces, everything needed for the release is now included in the build (powershells, resources, etc..), which greatly simplyfies the release pipeline.

Release Pipeline

The task group is now replaced by a single Azure Powershell task included in the build artifacts. Please refer to the release pipeline for more information.

The following task group parameters should be used as the powershell's arguments:

  • ArtifactsPath: -ArtifactsPath
  • ResourcePrefix: -ResourcePrefix
  • AzureResourceGroup: -ResourceGroupName
  • Location: -ResourceGroupLocation

The AdditionalTemplateParameters can simply be copied and added to the Script Arguments.

If you are using the Azure PowerShell task to retrieve the access policies from key vault, then this task should also be removed from the release pipeline as it is now also included in the deployment script.

You can copy the -keyvaultName argument to the new powershell arguments.