Service Bus Emulator doesn't respect persistent lifetime

[sebastienros]

I still experience Service Bus Emulator restarting every time I start my Aspire App Host. I add it to my app host like this:

builder.AddAzureServiceBus("servicebus")
	.RunAsEmulator(emulator => emulator
		.WithConfigurationFile("./sb-emulator-config.json")
		.WithLifetime(ContainerLifetime.Persistent));

In the console logs, I see the following message every time I restart the app host:

[sys] Found existing Container, but calculated lifecycle key doesn't match: ContainerName = (..), ContainerId = (..)

The exact reason why the lifecycle key never matches is beyond me, but it triggers a restart of the emulator, significantly slowing down my development loop.

Originally posted by @tormodfj in #7278

[MihuBot]

I'm a bot. Here are possible duplicate issues (I may be wrong):

• The service bus emulator is never persistent when marked as such #7071
• AddAzureServiceBus not Persistent #14309

[sebastienros]

See #14309

Can you check if your user secrets are enabled? That will make the emulator reuse the same password, otherwise a new one is generated of every run and the hash changes (rightfully so)

[tormodfj]

I did in fact not have user secrets enabled. The fix was as simple as stated in #14309 (comment):

After doing.

dotnet user-secrets init
dotnet user-secrets list

Parameters:serviceBus-sql-pwd = 0QN{.pG}twCdB5S1ur)4kk

Now it works as expected. I think it should be noted in the Docs.

Thanks a lot! And I agree with the quoted comment above that this should be noted somewhere in the docs. That way, the LLMs can be more helpful if others experience this behavior in the future 😃

[sebastienros]

An idea that was suggested is to try and detect this case and log a warning. Not sure if we can also detect if the user secrets is defined, but I think it should work since we have a utility class to handle these.

[afscrome]

I think I encountered a variant of this issue yesterday - a persistent Postgresql database stopped being able to authenticate after changing DOTNET_ENVIRONMENT in the app host's launchsettings.json.

I assume that by not using the Development environment, User Secrets weren't being added to IConfiguration, and so the secret wasn't being picked up.

[sebastienros]

@afscrome are you suggesting we could also display a warning in Production environment that use Persistent lifetime?

[afscrome]

I wasn't targeting production environment, but I was trying to introduce multiple Development environments - e.g. Development-Mock, Development-Real.

This way I could make a launch profile for each mode, change DOTNET_ENVIRONMENT, and then condition logic on builder.Environment.EnvironmentName in the app host.