Elias.Lundmark
Dec 4, 2023
visibility 5096
star star star star star
(2 votes)

Import Blobs and Databases to Integration Environments

In this blog, we are going to explore some new extensions to the Deployment API in DXP Cloud Services, specifically the ability to import databases and blobs via the API. Some caveats to consider before we jump into the details,

  1. Blob and database imports are limited to integration and ADE environments
  2. Database imports are only available when using -DirectDeploy.

Uploading and Deploying Databases

You can know supply a bacpac file to Add-EpiDeploymentPackage

$saslink = Get-EpiDeploymentPackageLocation
Add-EpiDeploymentPackage -SasUrl $saslink -Path “C:\MyDatabaseFiles\environmentname.cms.sqldb.20231106.bacpac”

Bacpac is the same format that is used when databases are exported along with the same naming convention, so that any database that is exported can easily be imported again.

Once the upload is done, we can simply pass it to Start-EpiDeployment

Start-EpiDeployment -DeploymentPackage (”environmentname.cms.sqldb.20231106.bacpac”,”cms.app.1.0.0.nupkg”) -TargetEnvironment “Integration” -DirectDeploy

This example deploys a nupkg at the same time, but that can be ommitted to just import a database. E.g., -DeploymentPackage “environmentname.cms.sqldb.20231106.bacpac”. As usual, you will be able to see the status of the deployment in the management portal, or Get-EpiDeployment.

Creating a writeable SAS URI to upload blobs

For quite some time now, we have had the possibility to create readable SAS URIs via the Deployment API. E.g.,

Get-EpiStorageContainerSasLink -Environment “Integration” -StorageContainer “mysitemedia”

You can now add a -Writable flag to this command which enables you to upload blobs to the container as well. You can use this SAS URI to write via HTTPS, or use with Azure Storage Explorer. If you are using Azure Storage Explorer, select connect to a Blob container or Directory

Then select Shared access signature URL (SAS), and paste the writeable SAS URL

Our hope is that this will make it easier to deploy an existing site to our Cloud Services, and allow you to export content from any environment and easily import it again. 

Dec 04, 2023

Comments

Ove Lartelius
Ove Lartelius Dec 4, 2023 04:14 PM

Nice! Love it! Made me wanted to try deploy a Alloy website to DXP to test. This is my experience. https://www.epinova.se/en/blog/2023/setup-website-in-dxp-integration/

Vincent
Vincent Dec 5, 2023 01:26 AM

Great feature and glad to see DXP keeps improving to provide better developer's experience. 

Mark Hall
Mark Hall Dec 21, 2023 03:08 PM

Just a heads up the flag should be -Writable not -Writeable  

Tomas Hensrud Gulla
Tomas Hensrud Gulla Feb 13, 2024 11:59 AM

Another heads up: -Writable is only possible for the Integration environment.

KennyG
KennyG Mar 11, 2024 09:08 PM

Is there a trick to get it to do both the CMS and Commerce databases at the same time? I was able to upload both but only able to specify one at a time.

Mar 12, 2024 08:41 AM

@KennyG it should be possible to deploy a CMS and Commerce database at the same time - give this a try!

Start-EpiDeployment -DeploymentPackage @('myapp.cms.sqldb.1.0.0.bacpac', 'myapp.commerce.sqldb.1.0.0.bacpac') -TargetEnvironment Integration -DirectDeploy

error Please login to comment.
Latest blogs
cms13-scan: A Deterministic CMS 13 Readiness Scanner

Every CMS 12 to CMS 13 upgrade I have looked at starts the same way. Someone opens the solution and starts hunting. A text search for the APIs

Adnan Zameer | Oct 12, 2026 |

Setting Up an Optimizely CMS 13 MCP Server Locally with Codex

Optimizely CMS 13 supports Model Context Protocol (MCP) , allowing AI tools such as Claude and Codex to interact with CMS content and metadata...

Mardy | Oct 12, 2026

Handling SixLabors.ImageSharp vulnerability warnings in Optimizely CMS 12 (unofficial)

UPDATED: Optimizely is officially working with SixLabors to find a solution, if possible; the work ID is CMS-57231. An official decision/announceme...

Cuong Nguyen Dinh | Oct 10, 2026

Optimizely CMS 12 on .NET 10: Fixing a Siteimprove TypeMismatchException

Recently, while upgrading an Optimizely CMS 12 solution from .NET 8 to .NET 10, we encountered a frustrating exception that initially looked like a...

Madhu | Oct 9, 2026 |