[deleted]
Show HN: Relay – Event-driven DevOps automation
11–20 of 34 posts
Re: Show HN: Relay – Event-driven DevOps automation
#12Hi everyone! PM for Relay here. Relay is an event-driven DevOps platform. It listens to events from 3rd party services like AWS, Datadog, PagerDuty, Jira and more to trigger simpler, smarter workflows that automate tedious tasks. A lot of existing solutions either require a lot of upfront DIY work (AWS Lambda or running your own script) or they weren’t built for DevOps teams (Zapier, IFTTT). Relay provides out-of-the…
Looks great! "Zapier for DevOps" would convey it a lot faster. It didn't click for me until I got to that part. I'm excited to try it out! A couple things: 1) Please, please support some other config file other than just YAML. Even JSON would be an improvement, since you wouldn't have to change your config reader library. YAML has been a miserable nightmare to use in other tools like Open API Spec. I'm not alone in m…
> 1) Please, please support some other config file other than just YAML.
Although we don't directly advertise it, you can in fact write a workflow in JSON and there's an underlying JSON interchange format that is authoritative in our system. We expect that any other languages we support would "compile" to this JSON format. What other languages are interesting to you? We've looked at CUE[0], HCL, and of course Puppet itself.
[0]: https://cuelang.org/
Re: Show HN: Relay – Event-driven DevOps automation
#13I think we can do the same things using github actions now. P.S we have self-hosted runners in our enviroment where each step is a docker container too. We have complex flows where we use Slack, Spinnaker(Webhooks), Terraform, PagerDuty ... and much more. Is there something better that we can achieve with this?
Hi,
This is a good question, thank you! The flow of events into our system is somewhat different than GitHub Actions. We're trying to be a consumer of all sorts of events, including, say, data published to AWS SNS or via a Docker Hub webhook[0]. All of that isn't quite in place yet, but we want to act more like an event broker than a CI/CD solution alone.
One concept we're throwing around is supporting CloudEvents[1] and dispatching workflows based on event types. If anyone has experience with CloudEvents we'd love to hear if that would be something useful to you.
[0]: https://github.com/relay-integrations/relay-dockerhub/blob/m...
Re: Show HN: Relay – Event-driven DevOps automation
#14Hi everyone! PM for Relay here. Relay is an event-driven DevOps platform. It listens to events from 3rd party services like AWS, Datadog, PagerDuty, Jira and more to trigger simpler, smarter workflows that automate tedious tasks. A lot of existing solutions either require a lot of upfront DIY work (AWS Lambda or running your own script) or they weren’t built for DevOps teams (Zapier, IFTTT). Relay provides out-of-the…
Where is Relay's data (configurations, step results/logs) stored?
Re: Show HN: Relay – Event-driven DevOps automation
#15I think we can do the same things using github actions now. P.S we have self-hosted runners in our enviroment where each step is a docker container too. We have complex flows where we use Slack, Spinnaker(Webhooks), Terraform, PagerDuty ... and much more. Is there something better that we can achieve with this?
Hi, This is a good question, thank you! The flow of events into our system is somewhat different than GitHub Actions. We're trying to be a consumer of all sorts of events, including, say, data published to AWS SNS or via a Docker Hub webhook[0]. All of that isn't quite in place yet, but we want to act more like an event broker than a CI/CD solution alone. One concept we're throwing around is supporting CloudEvents[1]…
I'm writing a book on Knative and have some material in there about CloudEvents. It's on the MEAP program and the relevant chapter was put up yesterday, as it happens: https://livebook.manning.com/book/knative-in-action/chapter-...
Re: Show HN: Relay – Event-driven DevOps automation
#16So I didn't see anything on your site on my cursory glance at it, but I'd like to know if you have any use cases replacing Jenkins Pipelines and Helm deployments into an OpenShift/Kubernetes environment? I'm writing a lot of Jenkins pipelines now and groovy is killing me!
Re: Show HN: Relay – Event-driven DevOps automation
#17Hi everyone! PM for Relay here. Relay is an event-driven DevOps platform. It listens to events from 3rd party services like AWS, Datadog, PagerDuty, Jira and more to trigger simpler, smarter workflows that automate tedious tasks. A lot of existing solutions either require a lot of upfront DIY work (AWS Lambda or running your own script) or they weren’t built for DevOps teams (Zapier, IFTTT). Relay provides out-of-the…
Where is Relay's data (configurations, step results/logs) stored?
It varies. We have a primary PostgreSQL database for non-sensitive data including some workflow configuration. We store sensitive data in Vault and logs in Google Cloud Storage. A bit more info here: https://relay.sh/docs/how-it-works/#where-and-how-is-my-data...
I'm happy to answer any questions about our storage and security architecture too!
Re: Show HN: Relay – Event-driven DevOps automation
#18Earlier quoted context omitted.
Hi, This is a good question, thank you! The flow of events into our system is somewhat different than GitHub Actions. We're trying to be a consumer of all sorts of events, including, say, data published to AWS SNS or via a Docker Hub webhook[0]. All of that isn't quite in place yet, but we want to act more like an event broker than a CI/CD solution alone. One concept we're throwing around is supporting CloudEvents[1]…
I'm writing a book on Knative and have some material in there about CloudEvents. It's on the MEAP program and the relevant chapter was put up yesterday, as it happens: https://livebook.manning.com/book/knative-in-action/chapter-...
Thank you! I'll take a look through this! Would it be okay if I sent you an email in the next week or two for follow-up questions?
Re: Show HN: Relay – Event-driven DevOps automation
#19What's the pricing model? I don't see it on the website
Re: Show HN: Relay – Event-driven DevOps automation
#20So I didn't see anything on your site on my cursory glance at it, but I'd like to know if you have any use cases replacing Jenkins Pipelines and Helm deployments into an OpenShift/Kubernetes environment? I'm writing a lot of Jenkins pipelines now and groovy is killing me!
We do have a Helm integration that might be able to help you out: https://relay.sh/integrations/helm/
The limiting factor right now would be whether your cluster is accessible to the internet, which of course isn't super common. We are working through what our story for connecting to on-prem infrastructure looks like, so if you can provide any additional details on your environment, it would be helpful!