Repository navigation
Use the configured ClickHouse host in tenant provisioning - #5
Merged
Merged
Conversation
Signed-off-by: theboringhumane <me@iamharsh.dev>
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.
Tenant provisioning currently advertises localhost when CH_HOST is absent, even when Lumen connects to a remote ClickHouse server. Use the first configured driver address for the default advertised host and keep its existing port selection. Explicit environment and Infisical CH_HOST overrides retain their precedence.
Tests cover DNS, IPv4, IPv6, multiple addresses, configuration precedence and explicit host/port overrides. Driver TLS, protocol, credentials and compression options remain unchanged. CI will run the existing race, integration, build and vet checks; a fresh Enterprise image still needs native endpoint qualification before deployment.