A robot for mapping github events into actionable HTTP payloads
983
Goose is a tool which simplifies gitops by mapping between "files/file patterns I care about" and "services that need to know about those changes".
We have found examples of services which require us to configure resources by clicking around UIs. This suffers from an inability to review the work that's done before it happens, making rollbacks more difficult and an inability to add automated tooling around it. GitOps solves this.
There are some natural struggles for adopting a gitops-oriented approach. First, services who want to offer gitops functionality would need to listen to repository webhooks (which are a bit of a pain to setup, especially for every repository). They'd also need to build functionality around checking out git repositories, which significantly changes the scope of their existing APIs.
To provide an easier experience for both application developers and framework teams, we're building an intermediary layer between the hooks that GitHub provides and the services which want to know about the changes.
The end goal is you simply:
The service sends events for both "VERIFY" actions, like when a pull request is created, as well as "COMMIT" actions, which are when the change actually needs to take place. For VERIFY actions, these will be represented in the PR status.
For information about how to setup & configure goose, please see GitHub. https://github.com/eBay/goose
Content type
Image
Digest
Size
41.2 MB
Last updated
over 4 years ago
docker pull ebay/goose