RELENG-6332 configure middleware through env #62
Merged
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
Hello tcarmet,My role is to assist you with the merge of this Status report is not available. |
Incorrect Jira projectThe Jira issue RELENG-6332 specified in the source |
UI was throwing invalid input when behind a nginx ingress Hard to get a picture of how the ingress behave, making reverse proxy config manageable through env vars. It was spotted that there was a typo in the config for the http scheme, which was decisive in finding the root cause of the issue
tcarmet
force-pushed
the
bugfix/RELENG-6332-invalid-input-ingress-conf
branch
from
0b52bef
to
f5578c0
Compare
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.
UI was throwing invalid input when behind a nginx ingress
Hard to get a picture of how the ingress behave, making
reverse proxy config manageable through env vars.
It was spotted that there was a typo in the config
for the http scheme, which was decisive in finding
the root cause of the issue