Run-time connection string updates

Is it possible in v3 to update the connection string at run-time? I am trying to iterate over several databases with different connection strings and apply the same migrations from a .dll to each database. I want to omit the .WithGlobalConnectionString runner builder extension (this won’t be necessarily known at startup) and just set the connection string in a loop.

My service provider is created like this:

static IServiceProvider CreateServices()
{
    return new ServiceCollection()
        .AddFluentMigratorCore()
        .ConfigureRunner(rb => rb
            .AddSqlServer()
            .WithMigrationsIn(typeof(SomeMigrationClass).Assembly))
        .AddLogging(lb => lb.AddFluentMigratorConsole())
        .BuildServiceProvider(false);
}

I am getting at the ProcessorOptions and attempting to set the connection string like this in my loop:

var migrationRunner = _serviceProvider.GetRequiredService<IMigrationRunner>();
var processorOptions = _serviceProvider.GetRequiredService<IOptionsSnapshot<ProcessorOptions>>().Value;

processorOptions.ConnectionString = "MYCONNECTIONSTRING";

migrationRunner.MigrateUp();

When I do this, the migrationRunner.Processor.ConnectionString is never changed. It uses the default “No Connection”. Am I doing something wrong?

[derekgreer]

Perhaps it would be better to pose the desired solution and then ask whether fluent migrator currently supports it.

Here’s what I’d say you want to do:

foreach(var client in clients)
{
    var migrator = _migratorFactory.CreateMigrator(client.ConnectionString);
    migrator.MigrateUp();
}

[fubar-coder]

@nZeus As a migration is something that you should only do at the start of your services, why don’t you just create your own service collection just for the migration services?

I don’t think that there is a need to have long-lived services with changing connection strings.

BTW: Adding SetConnectionString to the migration runner will most likely never happen. As I wrote, you can always create your own service collection and just set the connection string with a .WithGlobalConnectionString(connectionString) in the ConfigureRunner extension method.