feat: add kraken_base_url config for GraphQL proxy#3668
Merged
springfall2008 merged 1 commit intomainfrom Mar 27, 2026
Merged
Conversation
E.ON/Kraken's CloudFront WAF blocks requests from datacenter IPs (Hetzner). This adds a configurable base_url override so SaaS pods can route GraphQL queries through a Supabase edge function proxy instead of hitting Kraken's API directly. OSS users are unaffected — without the config key, the hardcoded provider URLs are used as before. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
d7f5325 to
c7f7342
Compare
|
@mgazza - I want to assist with documentation. I personally use EDF so can assist as needed there |
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
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.
Summary
kraken_base_urlconfig key toKrakenAPI.initialize()KRAKEN_BASE_URLSfor GraphQL queriesContext
E.ON/Kraken's CloudFront WAF blocks requests from datacenter IPs (e.g. Hetzner). Token refresh works via Supabase edge functions, but direct GraphQL queries from pods get HTTP 403. This change lets us configure a proxy URL per-provider so pods route through our edge function instead.
OSS users are unaffected — without the config key, the existing hardcoded provider URLs are used.
Test plan
kraken_base_urlin config → uses hardcoded URLs as beforekraken_base_urlset → pod uses proxy URL for GraphQL queriesfind-tariffssucceeds via proxy from Hetzner pod🤖 Generated with Claude Code