-
-
Notifications
You must be signed in to change notification settings - Fork 280
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
feat: Add NATS module #1003
feat: Add NATS module #1003
Conversation
✅ Deploy Preview for testcontainers-dotnet ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
…eption. Caused by a copy waste while doing the initial implementation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for your pull request 🙏. It looks good! I just have a few minor questions and some suggestions for improvements.
Co-authored-by: Andre Hofmeister <[email protected]>
Fix -user & -pass were missing a -, so --user and --pass is now used. Add long params instead, e.g --jetstream instead of -js Add Validatation, if either password or username is set, then both are required. Fix EscapeDataString on username and password.
…iklasfp/testcontainers-dotnet into feat/add-nats-server-container # Conflicts: # src/Testcontainers.Nats/NatsBuilder.cs
@HofmeisterAn How should we handle this, you can rebase and merge if you see it fitting, or let me know what you need done from me 😄 |
Ah, perhaps I misinterpreted it. I thought you were going to make changes according to the suggestion.
I am fine with the pull request; it looks good 👍, thanks! I can merge it later today when I am back home. Rebase, etc. is not necessary. |
@HofmeisterAn cool!! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, again 🙏.
What does this PR do?
This pr adds support for the official Nats Server image
It should roughly align with the Go version providing support for
.WithUsername
and.WithPassword
The container enables the http monitoring endpoints of Nats, and exposes the default Nats server ports:
It also adds methods for getting a Nats connection string and the url for the monitoring endpoint.
Why is it important?
I needed it for my own work, and thought I might as well share it.
And since Nats already has both Go and Node.js implementations, I guess others would benefit as well.
Related issues
N/A
How to test this PR
Tests has been added in this pr.
Run the tests in
./tests/Testcontainers.Nats.Tests