Skip to content

The Postgres development platform. Supabase gives you a dedicated Postgres database to build your web, mobile, and AI applications.

docs: deployments key changes (#45160)

Chris Chinchilla03eed4d5a434
diff --git a/apps/docs/content/guides/deployment/branching/configuration.mdx b/apps/docs/content/guides/deployment/branching/configuration.mdx
index 937edbec6fe..128f8695925 100644
--- a/apps/docs/content/guides/deployment/branching/configuration.mdx
+++ b/apps/docs/content/guides/deployment/branching/configuration.mdx
@@ -172,8 +172,6 @@ The following fields support the `encrypted:` syntax:
- `auth.publishable_key`
- `auth.secret_key`
- `auth.jwt_secret`
-- `auth.anon_key`
-- `auth.service_role_key`
**Auth - Email (SMTP)**
diff --git a/apps/docs/content/guides/telemetry/log-drains.mdx b/apps/docs/content/guides/telemetry/log-drains.mdx
index 9b5b8adfdd0..c2c7d069aef 100644
--- a/apps/docs/content/guides/telemetry/log-drains.mdx
+++ b/apps/docs/content/guides/telemetry/log-drains.mdx
@@ -47,7 +47,7 @@ Unsigned requests to HTTP endpoints are temporary and all requests will signed i
1. Create and deploy the edge function
-Generate a new edge function template and update it to log out the received JSON payload. For simplicity, we will accept any request with an Anon Key.
+Generate a new edge function template and update it to log out the received JSON payload. For simplicity, we will accept any request with a Publishable Key.
```bash
supabase functions new hello-world
@@ -86,7 +86,7 @@ Create an HTTP drain under the [Project Settings > Log Drains](/dashboard/projec
- Disable the Gzip, as we want to receive the payload without compression.
- Under URL, set it to your edge function URL `https://[PROJECT REF].supabase.co/functions/v1/hello-world`
-- Under Headers, set the `Authorization: Bearer [ANON KEY]`
+- Under Headers, set the `Authorization: Bearer [PUBLISHABLE KEY]`
<ProjectConfigVariables variable="publishableKey" />
diff --git a/apps/docs/content/guides/telemetry/metrics/grafana-cloud.mdx b/apps/docs/content/guides/telemetry/metrics/grafana-cloud.mdx
index e2d46419da7..081c23c3ab9 100644
--- a/apps/docs/content/guides/telemetry/metrics/grafana-cloud.mdx
+++ b/apps/docs/content/guides/telemetry/metrics/grafana-cloud.mdx
@@ -31,7 +31,7 @@ Grafana maintains a [Supabase integration guide](https://grafana.com/docs/grafan
2. Provide:
- Your Supabase project ref (e.g. `abcd1234`).
- The Metrics API endpoint: `https://<project-ref>.supabase.co/customer/v1/privileged/metrics`.
- - HTTP Basic Auth credentials (`service_role` / `sb_secret_...`).
+ - HTTP Basic Auth credentials (`sb_secret_...`).
3. Choose the scrape interval (1 minute recommended) and test the connection. Grafana Cloud will deploy an agent in the background that scrapes the Metrics API and forwards the data to Prometheus.
If you prefer to reuse an existing Grafana Agent deployment, configure an [integration pipeline](https://grafana.com/docs/grafana-cloud/send-data/agent/integrations/integration-reference/integration-supabase/) with the same URL and credentials.
diff --git a/apps/docs/content/guides/telemetry/metrics/grafana-self-hosted.mdx b/apps/docs/content/guides/telemetry/metrics/grafana-self-hosted.mdx
index 876bc233da4..cde68d3d82d 100644
--- a/apps/docs/content/guides/telemetry/metrics/grafana-self-hosted.mdx
+++ b/apps/docs/content/guides/telemetry/metrics/grafana-self-hosted.mdx
@@ -31,7 +31,7 @@ scrape_configs:
metrics_path: /customer/v1/privileged/metrics
scheme: https
basic_auth:
- username: service_role
+ username: username
password: '<secret API key (sb_secret_...)>'
static_configs:
- targets:
diff --git a/apps/docs/content/guides/telemetry/metrics/vendor-agnostic.mdx b/apps/docs/content/guides/telemetry/metrics/vendor-agnostic.mdx
index f600c139ab8..955b9f22b14 100644
--- a/apps/docs/content/guides/telemetry/metrics/vendor-agnostic.mdx
+++ b/apps/docs/content/guides/telemetry/metrics/vendor-agnostic.mdx
@@ -24,7 +24,7 @@ No matter which collector you use, you need to hit the Metrics API once per minu
metrics_path: /customer/v1/privileged/metrics
scheme: https
basic_auth:
- username: service_role
+ username: username
password: '<secret API key (sb_secret_...)>'
static_configs:
- targets: