From 84d6533cd4d28c682a8c4ed166b7433f7becff5b Mon Sep 17 00:00:00 2001 From: Daniel Mangum Date: Mon, 6 Jan 2025 17:11:14 -0500 Subject: [PATCH] pipelines: fix example supabase pipelines Fixes errors in supabase example pipelines. Signed-off-by: Daniel Mangum --- docs/data-routing/5-examples/24-supabase.md | 25 ++++++++++----------- 1 file changed, 12 insertions(+), 13 deletions(-) diff --git a/docs/data-routing/5-examples/24-supabase.md b/docs/data-routing/5-examples/24-supabase.md index 1963d2e0..665d6096 100644 --- a/docs/data-routing/5-examples/24-supabase.md +++ b/docs/data-routing/5-examples/24-supabase.md @@ -12,15 +12,15 @@ managed through a single interface. Supabase provides multiple ways to consume data from Golioth. The following examples will need credentials from Supabase. Create two -[secrets](/data-routing/secrets) based on the -[Service Role Key](https://supabase.com/docs/guides/api/api-keys#the-servicerole-key). -`$SUPABASE_KEY` should be the the Server Role Key while `$SUPABASE_SERVICE_KEY` -should take the form of 'Bearer -$Service_Role_Key'. For example, if the `Service Role Key` is `12345` than the `$SUPABASE_SERVICE_KEY`should be set to`Bearer -12345`. - -The first example is the simplest and uses the -[REST API](https://supabase.com/docs/guides/api). Assuming a database named +[secrets](/data-routing/secrets) based on the [Service Role +Key](https://supabase.com/docs/guides/api/api-keys#the-servicerole-key). +`$SUPABASE_API_KEY` should be the the Server Role Key while +`$SUPABASE_AUTH_HEADER` should take the form of `Bearer $Service_Role_Key`. For +example, if the `Service Role Key` is `12345` than the `$SUPABASE_AUTH_HEADER` +should be set to`Bearer 12345`. + +The first example is the simplest and uses the [REST +API](https://supabase.com/docs/guides/api). Assuming a table named `golioth_pipeline_basic` with the following columns: | id | created_at | temp | lat | long | @@ -28,22 +28,21 @@ The first example is the simplest and uses the Create the following Pipeline: - + The second example uses [Edge Functions](https://supabase.com/docs/guides/functions). While [Transformers](/data-routing/transformers) can be used to modify data, Edge Functions can be utilized further in the context of Supabase. -Assuming a database named `golioth_pipeline_advanced` with the following -columns: +Assuming a table named `golioth_pipeline_advanced` with the following columns: | id | created_at | ce-time | ce-subject | ce-type | ce-source | temp | lat | long | | -- | ---------- | ------- | ---------- | ------- | --------- | ---- | --- | ---- | Create the following Pipeline: - + Create a new Edge Function called `golioth-pipelines` with the following code: