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.

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

Add API to enable RabbitMQ #21

Open
SebastienDegodez opened this issue Jan 1, 2025 · 1 comment
Open

Add API to enable RabbitMQ #21

SebastienDegodez opened this issue Jan 1, 2025 · 1 comment
Labels
component/documentation Improvements or additions to documentation component/runtime Runtime behavior of test container component/settings Relates to API/settings availables keep-open Explicitily keep open kind/feature New feature

Comments

@SebastienDegodez
Copy link
Member

Reason/Context

The Microcks supports protocols like as WebSocket, MQTT, KAFKA and RabbitMQ.

Currently, the Microcks-testcontainers-dotnet project does not support asynchronous protocols.

I want to add support for RabbitMQ as I have experience with it from my previous company, and I believe support for this protocol can be good.

Description

There is a PR adding KAFKA support. Based on that, the goal is to add a new method in MicrocksContainerEnsemble and MicrocksAsyncMinionContainer.

Implementation ideas

Same Developer eXPerience as with test container java module

@lbroudoux lbroudoux added component/documentation Improvements or additions to documentation kind/enhancement Enhancement of existing feature component/runtime Runtime behavior of test container component/settings Relates to API/settings availables kind/feature New feature and removed kind/enhancement Enhancement of existing feature labels Jan 7, 2025
Copy link

github-actions bot commented Feb 7, 2025

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 30 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. Microcks is a Cloud Native Computing Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

@github-actions github-actions bot added the stale Stale due to inactivity label Feb 7, 2025
@lbroudoux lbroudoux added keep-open Explicitily keep open and removed stale Stale due to inactivity labels Feb 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/documentation Improvements or additions to documentation component/runtime Runtime behavior of test container component/settings Relates to API/settings availables keep-open Explicitily keep open kind/feature New feature
Projects
None yet
Development

No branches or pull requests

2 participants