From 85ecce300dca601b7a21724125d2fad7491157e8 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" Date: Wed, 28 Aug 2024 13:40:20 +0000 Subject: [PATCH] Commit changes made by code formatters --- runbooks/source/investigating-blocked-ingress-spikes.html.md.erb | 1 - 1 file changed, 1 deletion(-) diff --git a/runbooks/source/investigating-blocked-ingress-spikes.html.md.erb b/runbooks/source/investigating-blocked-ingress-spikes.html.md.erb index 5a65a9b8..ca04af77 100644 --- a/runbooks/source/investigating-blocked-ingress-spikes.html.md.erb +++ b/runbooks/source/investigating-blocked-ingress-spikes.html.md.erb @@ -24,4 +24,3 @@ Things to look at while investigating a spike in blocked access: It's important to clearly and efficiently communicate between the Cloud Platform team and user. It may be required to call an [incident](https://runbooks.cloud-platform.service.justice.gov.uk/incident-process.html). Where possible keep a record of findings as either part of the a Slack thread or Google document. Further issues can be raised in the Cloud Platform issue [tracker](https://github.com/ministryofjustice/cloud-platform/issues). -