Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

The service bus emulator is never persistent when marked as such #7071

Open
davidfowl opened this issue Jan 11, 2025 · 2 comments · May be fixed by #7136
Open

The service bus emulator is never persistent when marked as such #7071

davidfowl opened this issue Jan 11, 2025 · 2 comments · May be fixed by #7136
Assignees
@sebastienros
Labels
area-integrations Issues pertaining to Aspire Integrations packages azure Issues associated specifically with scenarios tied to using Azure
Milestone
9.1

Comments

@davidfowl
Copy link
Member

When marking the service bus emulator as persistent it still restarts. This is unfortunate because it takes a little bit to start up.

var serviceBus = builder.AddAzureServiceBus("bus")
                        .RunAsEmulator(c => c.WithLifetime(ContainerLifetime.Persistent))
                        .WithQueue("q");

It seems like the problem is:

We generate a new password every time, causing the container hash to change.
@davidfowl davidfowl added area-integrations Issues pertaining to Aspire Integrations packages azure Issues associated specifically with scenarios tied to using Azure labels Jan 11, 2025
@davidfowl davidfowl added this to the 9.1 milestone Jan 11, 2025
@sebastienros
Copy link
Member

it still restarts

It's not stopped, but I assume that since the "hash" changes then it does a restart of the same container (not sure how that works).

However the dependent container for sqledge is stopped completely, so I assume it needs to inherit the lifetime. I tried and this works well.

@sebastienros
Copy link
Member

I can also see the service being restarted even after setting a reusable password. The sqledge container is kept alive correctly after flowing the lifetime though.

@sebastienros sebastienros linked a pull request Jan 17, 2025 that will close this issue
Open
18 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sebastienros sebastienros

Labels
area-integrations Issues pertaining to Aspire Integrations packages azure Issues associated specifically with scenarios tied to using Azure
Projects
None yet
Milestone
9.1
Development

Successfully merging a pull request may close this issue.

Fix Azure ServiceBus persistent container support dotnet/aspire
2 participants
@davidfowl @sebastienros