21–30 of 34 posts
What's the pricing model? I don't see it on the website
Hi 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…
Besides it seems like this company (Relay) has gone to the effort of making a VScode language extension, which enables autocomplete and syntax checking in the YAML files. Which is cool.
Hi 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…
JSON is valid YAML, so that should "just work" already. Have you tried it?
Earlier quoted context omitted.
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?
Sadly, it doesn't seem to support SSH, so I can't use it to replace Fabric scripts.
I wrote an SSH step for you. Here's the source code:
https://github.com/relay-integrations/relay-ssh/blob/master/...
And since it isn't documented yet, here's how you would use it in a workflow:
steps:
- name: ssh
image: relaysh/ssh-step-exec
spec:
connection: !Connection {type: ssh, name: my-ssh-connection}
username: relay
port: 2222 # defaults to 22
knownHosts: |
server1.example.com ssh-rsa AAAAEXAMPLE
server2.example.com ssh-rsa AAAANOTHEREXAMPLE
# or
#strictHostKeyChecking: false
on:
- server1.example.com
- server2.example.com
input:
- whoami
- uptime
- cat /etc/passwd
Earlier quoted context omitted.
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…
I think the YAML hate is a bit exaggerated. It's not perfect but I would rather write out YAML than JSON or XML. Besides it seems like this company (Relay) has gone to the effort of making a VScode language extension, which enables autocomplete and syntax checking in the YAML files. Which is cool.
Earlier quoted context omitted.
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…
Earlier quoted context omitted.
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…
> Even JSON would be an improvement JSON is valid YAML, so that should "just work" already. Have you tried it?