Puppet Relay Offers Event-Driven Automation for DevOps Workflows – InApps Technology is an article under the topic Devops Many of you are most interested in today !! Today, let’s InApps.net learn Puppet Relay Offers Event-Driven Automation for DevOps Workflows – InApps Technology in today’s post !
Read more about Puppet Relay Offers Event-Driven Automation for DevOps Workflows – InApps Technology at Wikipedia
You can find content about Puppet Relay Offers Event-Driven Automation for DevOps Workflows – InApps Technology from the Wikipedia website
IT automation software provider Puppet has released into public beta its event-driven automation platform, Relay, software used to manage task-driven and model-driven automation. Relay comes with a number of pre-written workflows and connections to cloud platforms, tools, and APIs, including PagerDuty, GitHub, Datadog, Jira, Terraform, and Slack.
“Pretty much every major functional aspect of the system is pluggable, both by ourselves and by the community. All the specs and APIs are public, and every step of a workflow is something that anyone including ourselves, or including the user community, can build on their own,” said Puppet Chief Technology Officer Deepak Giridharagopal.
Written primarily in Go, the Relay workflow engine makes use of several other open source projects to achieve its goals. First, Ambassador, the open source Kubernetes-native API gateway for microservices built on the Envoy Proxy, handles the ingress of event data. It’s “like a service mesh, but without all of the complexity,” Giridharagopal said. Tekton, the open-source framework for creating CI/CD systems, provides a basic framework for handling workflows. Finally, Knative, the Kubernetes-based platform to deploy and manage modern serverless workloads, runs the workflow steps, all of which are containerized and available on GitHub, explained Alex Bilmes, vice president of growth at Puppet.
“We like to describe Relay as IFTTT or Zapier, but for DevOps,” said Bilmes. “It basically works by listening to all types of external events, whether it be a Splunk capacity alert firing, or a GitHub pull request being merged, or a new ECM instance coming online. From there, we can trigger a workflow that has a number of different steps that customers can arrange in whatever order they desire. A step could be provisioning an environment, or de-provisioning an [Amazon Web Services’] s3 bucket.”
Bilmes explained that users could edit workflows either directly in YAML or by using the visual interface, and the company offered a number of potential use cases, such as deleting underutilized cloud resources across different providers, providing incident response, enforcing security controls, or even automatically provisioning cloud infrastructure and deploying the latest versions of your software.
“There’s so many new building blocks out there, so many new APIs, it’s hard to keep up. There’s more choices in terms of how we build things than there’s ever been before. This embarrassment of choice is good, because it gives you a ton of options on how you build stuff, but I do think that there’s a big opportunity out there for people to build tools that don’t necessarily simplify by eliminating choices, but instead help you simplify and understand things by helping you wrap your arms around all the complexity,” said Giridharagopal. “That tends to be one of our governing principles behind what we’re trying to do with Relay. I harbor no illusions that people will shrink the size of their stack or consolidate into a smaller number of things, given how many choices there are, but I still deeply sympathize with their desire to simplify.”
Interested users can sign up for the public beta of Relay starting today.
Amazon Web Services is a sponsor of InApps Technology.
At this time, InApps Technology does not allow comments directly on this website. We invite all readers who wish to discuss a story to visit us on Twitter or Facebook. We also welcome your news tips and feedback via email: [email protected].
Source: InApps.net
List of Keywords users find our article on Google:
jira automation |
jira workflow |
jira automation email |
datadog jobs |
jira automation issue fields |
amazon relay |
splunk github |
pagerduty github |
devops workflows |
jira project automation |
jira slack |
splunk twitter |
automation for jira from email |
automation jira |
jira email automation |
jira automation send email |
automation for jira |
terraform api gateway |
jira automation based on email |
jira automation based on email address |
jira automation based on specific email address |
jira automation custom fields |
linux foundation events |
zapier jira |
relay amazon |
jira edit workflow |
edit workflow jira |
relay go amazon |
tekton tools review |
amazon relay requirements |
datadog to slack |
automation ideas in jira |
jira workflow automation |
jira portfolio vs splunk |
ats automation jobs |
puppet amazon |
relay resources jobs |
zapier aws s3 |
puppet github |
event-driven workflows |
dev ops workflows |
software open source provider ecm |
splunk jira |
automation for jira email |
event-driven workflow |
security puppet |
event driven workflow |
zapier github |
edit workflow in jira |
jira cloud automation |
jira custom workflow triggers |
workflow automation triggers jira |
ecm automation |
protective relay market |
jira for slack |
splunk devops |
automation for jira development[pull requests].status |
custom puppet |
envoy api gateway |
datadog slack |
github jira |
jira release workflow |
timing relay market |
puppet labs news |
relai app |
github datadog |
datadog github |
facebook puppet |
wikipedia relay |
datadog.yaml github |
how to create custom events in jira |
zapier facebook |
change issue type in jira service desk automation keyword |
jira zapier |
amazon tekton |
event driven automation |
puppet proxy |
event-driven automation |
ingress events 2022 |
jira automation fields |
tekton github |
create a custom event in jira cloud |
automation for jira development[pullrequests].status |
how to update a jira field automation cloud |
event drive automation |
amazon relay blocks |
quality-driven-software |
jira automation comment updates reply status |
datadog envoy |
jira terraform |
post function in jira |
how to update a jira field automation |
linkedin automation jira |
pagerduty jira |
slack linkedin |
automation for jira debugging |
ats linkedin |
event-based automation |
devops icon |
pagerduty terraform |
puppet automation |
edit jira workflow |
net core workflow engine |
zapier whatsapp business |
automation game engines |
model-driven app |
splunk alert |
twitter zapier |
automation for jira commented by group |
creating custom jira workflow and task templates |
datadog learning center |
jira automation slack |
model-driven apps |
jira datadog |
automation for jira data center |
event-based vision software |
pagerduty how to page someone |
terraform api gateway example |
how to edit workflow in jira |
jira automation scheduled |
jira workflow api |
jira automation comments |
jira how to edit workflow |
puppet api |
relay customer success |
whatsapp business zapier |
jira automated email |
jira cloud custom fields |
jira project automation email |
jira workflow edit |
open automation software |
where do you arrange jira custom field order? |
best practice jira workflow |
how to edit wikipedia protected page |
jira automation vs project automation |
relay engineer |
zapier teams |
automation for jira custom field |
how to edit jira workflow |
jira prevent users from editing custom field |
jira workflow automation triggers |
puppet datadog |
splunk bucket |
jira service desk automation custom field |
atlassian service desk-automation-api |
jira automation not working |
jira core workflow |
jira worflow |
professional puppet |
splunk update event |
github for jira |
business automation workflow |
github and jira |
Let’s create the next big thing together!
Coming together is a beginning. Keeping together is progress. Working together is success.