Migration Guide 25.2 [Prep GEN]

RabbitMQ objects migration

The new resource tag feature replaces the existing location awareness feature of Vidiflow but requires a migration for RabbitMQ exchanges, queues and messages.
This migration is required in installations

• that actively use the previous location awareness feature in Vidiflow, i.e. systems that use Vidiflow components with a non-empty ExecutionLocation in their start-up configuration, and,

• you want to execute tasks after the upgrade to 25.2 that were queued before the upgrade.

In all other scenarios the migration is recommended since it removes RabbitMQ objects that would otherwise clutter the RabbitMQ cluster.

You must start the migration before you update to 25.2.

Migration steps

1. Download and unzip this embedded ResourceTagMigration.zip to a Windows machine with access to the RabbitMQ cluster.

2. Adapt the unzipped …/net8.0/config/appsettings.json file with the RabbitMQ endpoint and credentials of your cluster.

3. Scale down all agent deployments in your existing installation.

4. Execute the migration tool with dotnet ResourceTagMigration or ResourceTagMigration.exe. The tool will abort if you have not scaled down all agent deployments before. It will provide log messages on the console to show the migration progress.

5. Once the migration has completed, you can now upgrade to 25.2.

6. Scale up all agent deployments.

Required secret goes here =>

Ressource Tags:

VC - existing vidicore site will be removed by location tag (location can only be set via location API in VC)