Trouble migrating media libraries from Azure

Hi guys,

We're working on a v13 => XbK migration. Everything is advancing as we'd like BUT. I have some question about image migration.

I'm currently doing this test:

  • Have a v13 website running locally with storage configures on Azurite. All locally.

  • Have a XbK website running, also configured on Azurite (the same)

  • Configure the migration tool to point to the correct places

  • Run --media-libraires with bypass

Both websites works well with Azurite, no problem for me there. The goal is to try the migration between Azure managed sites.

The result: it tried to retrieve the image locally.

Kentico.Xperience.UMT.Services.AssetManager[0] File C:\PathToMyLocalCMSFolder\src\CMS\SiteName\media\MyMediaLibrary\anImage does not exist

Expected result: it reads the configuration files to see both are configured for Azure storage and uses that instead.

As it runs locally, I directly modified the default web-config and appsettings-json to be sure it was taken into account (instead of appsettings-Development).

Am I missing something ?

Have a nice day you all :)

[edit] some formating are weird but cloudfare was being a bit of a pain. Seems it does not like file names ^^

Tags:
Content hub Media Library Migration / upgrade Azure
0

Answers

https://github.com/Kentico/xperience-by-kentico-kentico-migration-tool/blob/master/KVA/Migration.Tool.Source/Services/AssetFacade.cs#L518

pathParts.Add(toolConfiguration.KxCmsDirPath);
if (cmsUseMediaLibrariesSiteFolder)
{
    pathParts.Add(ksSite.SiteName);
}
pathParts.Add(DirMedia);
pathParts.Add(ksMediaLibrary.LibraryFolder);

Seems it always add the root folder of the CMS.

Does that mean we always have to move our assets locally to do a migration ?

Will it be capable of exporting to azure cloud the values or do we have to do everything localy ? When I read the code, I have the feeling it only manages locally. Do I have to download everything from blob storage, migrate, reupload everything to blob storage ?

0

To response this discussion, you have to login first.