feat: add origin protection key enforcement for envoy in lds.supabase.yaml
#1328
Conversation
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
hf
force-pushed
the
hf/opk-lds-supabase
branch
from
b13dd06 to
7636080
Compare
hf
commented
Nov 20, 2024
| - header: | ||
| name: sb-opk | ||
| string_match: | ||
| exact: supabase_origin_protection_key |
There was a problem hiding this comment.
Replaced by the init scripts here: https://github.com/supabase/infrastructure/pull/20665/files#diff-a5d511773da8bfc9e40cc61e37c5d1c7f0eb22f7621975238124eef85bc76af6R75
samrose
requested changes
Nov 20, 2024
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.
Adds enforcement for the origin protection key header value in the
lds.supabase.yamlEnvoy config file. It is generated by runningscripts/update-envoy-config.shinworkerof the infra repo (PR).Based on: