Update how kong.yml is used to configure Supabase in dev vs. prod #3384
Conversation
This file contains 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
|
|
manekenpix
requested changes
Apr 2, 2022
|
Fixed, thanks for catching. |
Co-authored-by: Josue <manekenpix@fastmail.com>
DukeManh
approved these changes
Apr 2, 2022
Kevan-Y
approved these changes
Apr 2, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Yesterday @DukeManh, @Kevan-Y and I tried to insert all the feeds into Supabase on staging. We found that our
service_role_keywouldn't work, and even ouranon_keywon't pass verification. The issue is that we are hard-coding the keys into ourkong.ymlconfig: https://github.com/Seneca-CDOT/telescope/blob/master/docker/supabase/volumes/api/kong.yml#L6-L12These need to match the keys we use on staging and production.
I've created new
kong.ymlfiles for staging and production, and sent to @manekenpix to add to the servers. Once those are in place, we can do this change.@manekenpix, please confirm that the paths I have used for production match what you do with these files (I think I'm right, but it's untested).
Fixes #3381.