From b57b4f05dec3cd575f396c77aef4cb18d6d60c29 Mon Sep 17 00:00:00 2001 From: Copple <10214025+kiwicopple@users.noreply.github.com> Date: Wed, 17 May 2023 12:19:42 -0700 Subject: [PATCH] dupicates --- apps/docs/pages/guides/platform/maturity-model.mdx | 5 ----- 1 file changed, 5 deletions(-) diff --git a/apps/docs/pages/guides/platform/maturity-model.mdx b/apps/docs/pages/guides/platform/maturity-model.mdx index 3b3b95298f6..3511f39a7b2 100644 --- a/apps/docs/pages/guides/platform/maturity-model.mdx +++ b/apps/docs/pages/guides/platform/maturity-model.mdx @@ -34,11 +34,6 @@ Resources: - [Managing environments](/docs/guides/cli/managing-environments) - [Access Control](/docs/guides/platform/access-control) -Resources: - -- [Database migrations](/docs/guides/getting-started/local-development#database-migrations) -- [PGAudit for Postgres](/docs/guides/getting-started/local-development#database-migrations) - ## Enterprise For a more secure setup, consider running your workload across several organizations. It's a common pattern to have a Production organization which is restricted to only those team members who are qualified to have direct access to production databases.