PostgreSQL persistent lifetime not working when setting --environment in Integration test

[amolenk]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

I've written integration tests using DistributedApplicationTestingBuilder. To shorten the test run, I use Persistent lifetime for my PostgreSQL container. I also set the environment to 'Testing' so I can detect that it's a test run in my AppHost:

var appHost = await DistributedApplicationTestingBuilder.CreateAsync<Projects.AspireTest_AppHost>([
    "--environment=Testing",
], cancellationToken);

When running the test, the PostgreSQL container is restarted each time.

If I remove the environment parameter, the PostgreSQL doesn't restart each time and works as expected:

var appHost = await DistributedApplicationTestingBuilder.CreateAsync<Projects.AspireTest_AppHost>(cancellationToken);

I can also set other parameters without breaking the Persistent Lifetime functionality. It's only when settings the --environment parameter that the container restarts each time.

Expected Behavior

I expect the PostgreSQL container not to restart, independent of whether or not I'm setting the environment.

Steps To Reproduce

• Create an Aspire Starter app (aspire-starter template)
• Add a test project (aspire-xunit template)
• Add the Aspire.Hosting.PostgreSQL package to the AppHost
• Add the PostgreSQL container:

  var postgres = builder.AddPostgres("postgres")
      .WithLifetime(ContainerLifetime.Persistent);

• Add the environment parameter:

  var appHost = await DistributedApplicationTestingBuilder.CreateAsync<Projects.AspireTest_AppHost>([
          "--environment=Testing",
  ], cancellationToken);

• Run the test a couple of times. Each time, the PostgreSQL container will restart (I monitor this in the Docker Desktop dashboard)
• Remove the --environment parameter
• Run the test a couple of times again. The PostgreSQL container will stay alive and not restart.

Exceptions (if any)

No response

.NET Version info

.NET version 9.0.100

Anything else?

.NET Aspire version 9.2.1

[Kralizek]

What if I wanted to force this behavior after the bug fix?

I also use a persistent container but I see the advantage of running tests against a new one while not touching the one used at dev time.

[amolenk]

@Kralizek You can change the lifetime of the containers before running the tests. @DamianEdwards has a sample of this: https://github.com/dotnet/aspire-samples/blob/0c27e4e3bac5f102db1002fd2e0e1ba894e1009a/tests/SamplesIntegrationTests/Infrastructure/DistributedApplicationExtensions.cs#L39-L53