MigrationWorker scale to 0

[huberttrueselftrueme]

Hi everyone.

I am working with aspire and create MigrationWorker project as in https://learn.microsoft.com/en-us/dotnet/aspire/database/ef-core-migrations

I want it to configure in a way that my instance will go stale to 0 after migrations are done.

My setup is

var migrations = builder.AddProject<MigrationWorker>(OrchestrationResources.Migrations)
    .PublishAsAzureContainerApp((config, app) =>
    {
        app.Template.Scale.MinReplicas = 0;
        app.Template.Scale.MaxReplicas = 1;
    })
    .WithEnvironment(c =>
    {
        if (builder.ExecutionContext.IsPublishMode)
        {
            c.EnvironmentVariables["ASPNETCORE_ENVIRONMENT"] = builder.Configuration["ASPNETCORE_ENVIRONMENT"];
            c.EnvironmentVariables["DOTNET_ENVIRONMENT"] = builder.Configuration["DOTNET_ENVIRONMENT"];   
        }
    })
    .WaitFor(postgresDb)
    .WaitFor(storageBlob)
    .WithReference(serviceBus)
    .WithReference(postgresDb);

And worker is self

  public class Worker : BackgroundService
{
  public const string ActivitySourceName = "Migrations";
  private static readonly ActivitySource s_activitySource = new(ActivitySourceName);
  
  private readonly ILogger<Worker> logger;
  private readonly ILifetimeScope lifetimeScope;
  private readonly IHostApplicationLifetime hostApplicationLifetime;

  public Worker(ILogger<Worker> logger, ILifetimeScope lifetimeScope, IHostApplicationLifetime hostApplicationLifetime)
  {
      this.logger = logger;
      this.lifetimeScope = lifetimeScope;
      this.hostApplicationLifetime = hostApplicationLifetime;
  }

  protected override async Task ExecuteAsync(CancellationToken cancellationToken)
  {
      using var activity = s_activitySource.StartActivity("Migrating database", ActivityKind.Client);
      try
      {
          //await EnsureDatabaseAsync(cancellationToken);
          await RunMigrationAsync(cancellationToken);
          await SeedDataAsync(cancellationToken);   
      }
      catch (Exception ex)
      {
          activity?.AddException(ex);
          logger.LogError(ex, "An error occurred while migrating the database.");
          throw;
      }

      hostApplicationLifetime.StopApplication();
  }

Issue:
After deploying my application, I notice in the Aspire Dashboard that the MigrationWorker remains running with 1 instance, generating unnecessary costs for the entire month. I expect it to scale down to 0 instances after completing the database migrations, but it doesn’t.

Question:
How can I configure the MigrationWorker in my .NET Aspire project to automatically scale to 0 instances after migrations are complete, preventing it from running continuously and incurring ongoing costs?