Skip to content

Commit 5fe1a96

Browse files
authored
Fix typo (#335)
1 parent 68aeef1 commit 5fe1a96

File tree

1 file changed

+7
-6
lines changed
  • docs/guides/gcp/real-time-events

1 file changed

+7
-6
lines changed

docs/guides/gcp/real-time-events/index.md

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -234,13 +234,14 @@ any in error, they should be investigated. Any questions can be directed to
234234
Event handlers can be shut-off by setting:
235235

236236
- [GCP > Turbot > Event Handlers > PubSub](https://turbot.com/guardrails/docs/mods/gcp/gcp/policy#gcp--turbot--event-handlers--pubsub)
237-
to **Enforce: Configured**
237+
to **Enforce: Not Configured**
238238
- [GCP > Turbot > Event Handlers > Logging](https://turbot.com/guardrails/docs/mods/gcp/gcp/policy#gcp--turbot--event-handlers--logging)
239-
to **Enforce: Configured**. Turbot will perform the required Terraform runs to
240-
destroy the event handler infrastructure. **Note:** Deleting an GCP project
241-
out of a Guardrails workspace will not automatically decommission the event handlers. Event
242-
Handlers must be set explicitly destroyed before removing the project from
243-
a Guardrails workspace.
239+
to **Enforce: Not Configured**. Turbot will perform the required Terraform runs to
240+
destroy the event handler infrastructure.
241+
242+
> [!NOTE]
243+
> Deleting a GCP project out of a Guardrails workspace will not automatically decommission the event handlers. Event Handlers must be set explicitly destroyed before removing the project from a Guardrails workspace.
244+
244245

245246
## When to decommission Event Handlers
246247

0 commit comments

Comments
 (0)