feat(server): support InfluxDB behind proxy under subpath #5940
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
sranka
changed the title
sranka
force-pushed
the
5096/influxdb_context_path
branch
from
3cc72d6 to
85db81a
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.
Closes #5096
Briefly describe your proposed changes:
This PR changes the communication with InfluxDB so that a configured InfluxDB connection URL path is preserved as a context path when calling InfluxDB APIs. It works fine with InfluxDB OSS. InfluxDB Enterprise connections still must be configured without a context path (a proxy path), the cluster design requires doing so.
What was the problem?
InfluxDB Connection URL context path was ignored, and paths of InfluxDB APIs were directly used.
What was the solution?
API paths are appended to the configured InfluxDB connection path.