From 30f607cb7dda9da33f5982246e5407ac079d6ccc Mon Sep 17 00:00:00 2001
From: Matt Shaver <60105315+matthewshaver@users.noreply.github.com>
Date: Wed, 4 Dec 2024 16:48:12 -0500
Subject: [PATCH] Removing old snippet

---
 website/docs/docs/build/hooks-operations.md                    | 2 --
 website/docs/reference/dbt-jinja-functions/this.md             | 2 --
 .../docs/reference/project-configs/on-run-start-on-run-end.md  | 2 --
 website/docs/reference/resource-configs/pre-hook-post-hook.md  | 2 --
 website/snippets/hooks-to-grants.md                            | 3 ---
 5 files changed, 11 deletions(-)
 delete mode 100644 website/snippets/hooks-to-grants.md

diff --git a/website/docs/docs/build/hooks-operations.md b/website/docs/docs/build/hooks-operations.md
index 6cec2a673c0..842d3fb99a3 100644
--- a/website/docs/docs/build/hooks-operations.md
+++ b/website/docs/docs/build/hooks-operations.md
@@ -40,8 +40,6 @@ Hooks are snippets of SQL that are executed at different times:
 
 Hooks are a more-advanced capability that enable you to run custom SQL, and leverage database-specific actions, beyond what dbt makes available out-of-the-box with standard materializations and configurations.
 
-<Snippet path="hooks-to-grants" />
-
 If (and only if) you can't leverage the [`grants` resource-config](/reference/resource-configs/grants), you can use `post-hook` to perform more advanced workflows:
 
 * Need to apply `grants` in a more complex way, which the dbt Core `grants` config doesn't (yet) support.
diff --git a/website/docs/reference/dbt-jinja-functions/this.md b/website/docs/reference/dbt-jinja-functions/this.md
index f9f2961b08f..7d358cb6299 100644
--- a/website/docs/reference/dbt-jinja-functions/this.md
+++ b/website/docs/reference/dbt-jinja-functions/this.md
@@ -20,8 +20,6 @@ meta:
 
 ## Examples
 
-<Snippet path="hooks-to-grants" />
-
 ### Configuring incremental models
 
 <File name='models/stg_events.sql'>
diff --git a/website/docs/reference/project-configs/on-run-start-on-run-end.md b/website/docs/reference/project-configs/on-run-start-on-run-end.md
index 74557839f11..347ce54ab63 100644
--- a/website/docs/reference/project-configs/on-run-start-on-run-end.md
+++ b/website/docs/reference/project-configs/on-run-start-on-run-end.md
@@ -27,8 +27,6 @@ A SQL statement (or list of SQL statements) to be run at the start or end of the
 
 ## Examples
 
-<Snippet path="hooks-to-grants" />
-
 ### Grant privileges on all schemas that dbt uses at the end of a run
 This leverages the [schemas](/reference/dbt-jinja-functions/schemas) variable that is only available in an `on-run-end` hook.
 
diff --git a/website/docs/reference/resource-configs/pre-hook-post-hook.md b/website/docs/reference/resource-configs/pre-hook-post-hook.md
index bd01a7be840..ee3c81b0fd6 100644
--- a/website/docs/reference/resource-configs/pre-hook-post-hook.md
+++ b/website/docs/reference/resource-configs/pre-hook-post-hook.md
@@ -160,8 +160,6 @@ import SQLCompilationError from '/snippets/_render-method.md';
 
 ## Examples
 
-<Snippet path="hooks-to-grants" />
-
 ### [Redshift] Unload one model to S3
 
 <File name='model.sql'>
diff --git a/website/snippets/hooks-to-grants.md b/website/snippets/hooks-to-grants.md
deleted file mode 100644
index d7586ec53ca..00000000000
--- a/website/snippets/hooks-to-grants.md
+++ /dev/null
@@ -1,3 +0,0 @@
-
-In older versions of dbt, the most common use of `post-hook` was to execute `grant` statements, to apply database permissions to models right after creating them. We recommend using the [`grants` resource config](/reference/resource-configs/grants) instead, in order to automatically apply grants when your dbt model runs.
-