configuration to be able to remove x-krakend headers #728
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
meshenka
force-pushed
the
feature/remove-krakend-headers
branch
3 times, most recently
from
dfc5da5
to
330592c
Compare
Signed-off-by: Sylvain Gogel <[email protected]>
meshenka
force-pushed
the
feature/remove-krakend-headers
branch
from
330592c
to
35539a8
Compare
meshenka
changed the title
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.
start of a potential fix for #727
Basically i add in core package a variable and wrap everywhere Krakend errors in a condition of this flag set at startup.
WDYT?
Next: well it definitely needs tests, it is just a Proof of Concept making sure i am in the righ track