fix kong configuration for functions service #99
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.
What kind of change does this PR introduce?
Kong configuration is incorrect: requests to service
supabase-functions
are routed tofunctions
which doesn't existsWhat is the current behavior?
Currently configuration for kong is as follows:
But the
functions
dns name doesn't exists, and it is hardwired in the code.What is the new behavior?
Now the configuration is instead using the correct naming used for all other services:
Of course, in this example
zupa-supabase-functions
is the name of the service,Additional context
Notes: replaces PR #75