-
Notifications
You must be signed in to change notification settings - Fork 193
feat: add nats service #380
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
base: master
Are you sure you want to change the base?
Conversation
c95cb55 to
fd5ecec
Compare
Signed-off-by: Tom Bojer <t.bojer@shopware.com>
fd5ecec to
a90bc32
Compare
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #380 +/- ##
==========================================
+ Coverage 55.41% 60.02% +4.60%
==========================================
Files 46 48 +2
Lines 4125 3655 -470
==========================================
- Hits 2286 2194 -92
+ Misses 1511 1111 -400
- Partials 328 350 +22 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
@tombojer could you please fix linter issues? |
Signed-off-by: Tom Bojer <t.bojer@shopware.com>
|
@pasha-codefresh The tests are now passing. Ping me if I need to do something else. |
This pull request introduces a new notification service for NATS, adding support for sending messages via NATS.
Parameters
This notification service is capable of sending simple messages via Nats.
nats://nats:4222Example
Resource Annotation: