Instatus: Create incident when important github action fails

[bnchrch]

Overview

Creates or resolves an incident on the internal instatus page if an action is passing or failing

Notes for reviewers

1. Could not find documentation for passing any type of arguments to a instatus template. So we cannot specify what failed in the incident
2. I had the thought of making it a named action but it did not provide much DRYness to be worth it
3. This was tested out in our test repo here: https://github.com/airbytehq/github-workflow-test-repo-base/actions/workflows/trigger_ci_failure_for_fun.yml

[evantahler]

That's a rather reasonable payload :D

[evantahler]

Is instastatus smart enough to know which named service the incident belongs to based on the action name or something like that? Or, since we are using the same INSTATUS_CONNECTOR_CI_WEBHOOK_URL, are these incidents all in the same service?

[evantahler]

Could not find documentation for passing any type of arguments to a instatus template. So we cannot specify what failed in the incident

Maybe... multiple URLS?

[bnchrch]

Unfortunately small payload means much less context.

So the webhook url (and as a result the instatus template) is the area that "knows" what service this relates too.

This means that we have two instatus services

• Platform Critical Github Actions
• Connector Critical Github Actions

which each have a unique template

and each of those templates have a unique webhook url

One of them is defined in our secrets as INSTATUS_CONNECTOR_CI_WEBHOOK_URL and the other INSTATUS_PLATFORM_CI_WEBHOOK_URL

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
airbyte-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Sep 21, 2023 11:17pm