Conversation
This change introduces the ability for the activity-apiserver to connect to a clickhouse database using a secure connection. A client certificate is expected to be used to connect to clickhouse.
This change introduces the ability for the [activity-apiserver](https://github.com/datum-cloud/activity/blob/main/docs/components/apiserver-architecture.md) to connect to a clickhouse database using a secure connection. A client certificate is expected to be used to connect to clickhouse. See [Clickhouse's Golang library docs](https://clickhouse.com/docs/integrations/go#using-tls) for more information. --- Relates to https://github.com/datum-cloud/engineering/issues/90
ecv
approved these changes
Dec 23, 2025
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.
I was still having issues applying the migrations built in datum-cloud/engineering#8 because the
apply_migrations()function wasn't using the secure configuration. I also realized that the current approach to building up the client command wouldn't be very flexible for consumers.I adjusted the script so users can now just leverage the
CLICKHOUSE_CLIENT_EXTRA_ARGSenvironment variable to inject additional arguments into the migration commands.I pointed the staging environment at the migrations file in this branch so I could confirm that migrations executed successfully:
Relates to datum-cloud/enhancements#536