Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request adds support for a LavinMQ integration, including unit tests.
Documentation has been created under: dotnet/docs-aspire#2634
This fulfils the proposal outlined in #477
Please note - Unlike RabbitMQ, LavinMQ does not support configuration utilising environmental variables.
As such, the default credentials of
guest:guest
are used in this implementation, with a virtual host of/
User management and virtual host management can be performed using the LavinMQ management UI, which is built in.
Utilising AddConnectionString, a custom post configured instance of lavinmq could be configured and passed down to consuming (reference) apps, but thats outside the scope of the actual container resource.
LavinMQ is wire compatible with AMQP 0-9-1, meaning we can reuse the RabbitMQ.Client to connect to this.
Its a drop in for it in reality - meaning the existing MassTransit extensions will work with this too.
As such - the health check added utilises the
AspNetCore.HealthChecks.RabbitMQ
package, as their isn't a native one for LavinMQ. It's fully functional though as I use it in a production AKS cluster with MassTransit.