-
Notifications
You must be signed in to change notification settings - Fork 14
/
Copy pathservices.yaml
45 lines (44 loc) · 1.86 KB
/
services.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
# This work is dual-licensed under Creative Commons Zero v1.0 Universal and GNU General Public License v3.0 or later.
# The file containts example code. Replace the values with information that is pertinent to your project.
service:
- service:
name: GitLab
url: https://gitlab.com
status:
- https://status.gitlab.com/
description: If GitLab becomes unavailable, the Project will continue to operate in its current state. The disruption would only impact the team's ability to update code on the instances.
- service:
name: StatusCake
url: https://app.statuscake.com/
status:
- https://twitter.com/StatusCakeTeam
description: If there is a disruption in the StatusCake service, the Incident Response team will be notified by email.
- service:
name: OpsGenie
url: https://app.opsgenie.com/alert/
status:
- https://status.opsgenie.com/
- https://twitter.com/opsgenie
description: If there is a disruption in the OpsGenie service, all alerts automatically get delivered to the team via email.
- service:
name: Jira
url: https://project.atlassian.net/
status:
- https://twitter.com/JIRA
description:
- service:
name: Slack
url: https://slack.com/
status:
- https://status.slack.com/
- https://twitter.com/SlackStatus
backup: https://chat.google.com/
description:
- service:
name: AWS
url: https://signin.aws.amazon.com/console
status:
- http://status.aws.amazon.com/
description: |
If needed, you can [manage and create new servers](https://console.aws.amazon.com/ec2/v2/home).
In case of a **significant** disruption, after receiving approval from our Authorizing Official, the Contractor's team will deploy a new instance of the entire system to a different region.