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 NATS support #1

Closed
Jeffail opened this issue Sep 24, 2016 · 3 comments
Closed

Add NATS support #1

Jeffail opened this issue Sep 24, 2016 · 3 comments

Comments

@Jeffail
Copy link
Collaborator

Jeffail commented Sep 24, 2016

Add support for NATS as an input and as an output.

http://nats.io/
https://github.com/nats-io/gnatsd

@joeblew99
Copy link

I came here to make an issue for this . You read my mind.

I am really interested in benthos. It's a highly useful / practical thing.

I am also interested is using flogo ( on github ) with benthos.
They both compliment each other very nicely.

Flogo is interesting in that you described a flow and can then compile it to golang.

I am also thinking that all these systems need to hook into a service discovery system such as etcd so that when an endpoint changes they adapt.
Flagz on github can do this without the using process restarting

Since your using this for real world stuff am curious of your opinions

@Jeffail
Copy link
Collaborator Author

Jeffail commented Apr 18, 2017

Hey @joeblew99, I haven't seen flogo before but I'll check it out, sounds interesting. Etcd support would be great, I hadn't initially planned for it so at this stage it might take me a while to consider how I'd integrate it.

@Jeffail Jeffail closed this as completed May 17, 2017
@Jeffail Jeffail moved this from TODO to In Progress in Benthos Features May 17, 2017
@Jeffail Jeffail moved this from In Progress to Review in Benthos Features May 17, 2017
@Jeffail Jeffail moved this from Review to Done in Benthos Features May 17, 2017
@joeblew99
Copy link

@Jeffail thanks !!

ghballiet referenced this issue in ghballiet/benthos Sep 5, 2018
…etta to master

* commit '030eaad086c6624c235b7072e1baee96e2f4b2fa':
  perhaps this will work
peczenyj referenced this issue in peczenyj/connect Aug 4, 2023
…1988 and it was easy to fix

> $ govulncheck ./...
> Using go1.20.7 and govulncheck@v1.0.0 with vulnerability data from https://vuln.go.dev (last modified 2023-08-02 20:33:39 +0000 UTC).
>
> Scanning your code and 1323 packages across 269 dependent modules for known vulnerabilities...
>
> === Informational ===
>
> Found 1 vulnerability in packages that you import, but there are no call
> stacks leading to the use of this vulnerability. You may not need to
> take any action. See https://pkg.go.dev/golang.org/x/vuln/cmd/govulncheck
> for details.
>
> Vulnerability #1: GO-2023-1988
>     Improper rendering of text nodes in golang.org/x/net/html
>   More info: https://pkg.go.dev/vuln/GO-2023-1988
>   Module: golang.org/x/net
>     Found in: golang.org/x/net@v0.8.0
>     Fixed in: golang.org/x/net@v0.13.0

enjoy

Signed-off-by: Tiago Peczenyj <tpeczenyj@weborama.com>
Jeffail added a commit that referenced this issue Aug 8, 2023
…1988 and it was easy to fix (#2029)

> $ govulncheck ./...
> Using go1.20.7 and govulncheck@v1.0.0 with vulnerability data from https://vuln.go.dev (last modified 2023-08-02 20:33:39 +0000 UTC).
>
> Scanning your code and 1323 packages across 269 dependent modules for known vulnerabilities...
>
> === Informational ===
>
> Found 1 vulnerability in packages that you import, but there are no call
> stacks leading to the use of this vulnerability. You may not need to
> take any action. See https://pkg.go.dev/golang.org/x/vuln/cmd/govulncheck
> for details.
>
> Vulnerability #1: GO-2023-1988
>     Improper rendering of text nodes in golang.org/x/net/html
>   More info: https://pkg.go.dev/vuln/GO-2023-1988
>   Module: golang.org/x/net
>     Found in: golang.org/x/net@v0.8.0
>     Fixed in: golang.org/x/net@v0.13.0

enjoy

Signed-off-by: Tiago Peczenyj <tpeczenyj@weborama.com>
Co-authored-by: Ashley Jeffs <ash@jeffail.uk>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Development

No branches or pull requests

2 participants