docs: Fix "anon_key" secret name on "Scheduling Edge Functions" page#2527
Closed
everettbu wants to merge 1 commit into
Closed
docs: Fix "anon_key" secret name on "Scheduling Edge Functions" page#2527everettbu wants to merge 1 commit into
everettbu wants to merge 1 commit into
Conversation
In the SQL to create 2nd secret the name "publishable_key" is used, but in the CRON SQL another key is referenced with the name "anon_key"
github-actions
Bot
added
the
documentation
Author
|
Upstream PR was closed or merged. Code is synced via branch mirror. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Mirror of supabase/supabase#38146
Original author: savchenkoa
I have read the CONTRIBUTING.md file.
YES
What kind of change does this PR introduce?
Docs fix on this page: https://supabase.com/docs/guides/functions/schedule-functions
In the SQL to create 2nd secret the name "publishable_key" is used, but in the CRON SQL another key is referenced with the name "anon_key":
What is the current behavior?
Please link any relevant issues here.
What is the new behavior?
Feel free to include screenshots if it includes visual changes.
Additional context
Add any other context or screenshots.