Reference Clickhouse credentials in secret

[namm2]

Use secretKeyRef to not expose Clickhouse credentials into runtime environment

[CLAassistant]

All committers have signed the CLA.

[HamseTelia]

Could we also please add the clickhouse user's password to be referenced from a secret clickhouse.config.users.appUserPassword. Like suggested here: #125

clickhouse:
  config:
    users:
      # Existing inline password support (for backward compatibility)
      appUserPassword: "hyperdx"
      otelUserPassword: "otelcollectorpass"
      otelUserName: "otelcollector"
      
      # NEW: External secret support
      useExternalSecret: false
      externalSecret:
        name: ""
        appUserPasswordKey: "app-user-password"

[namm2]

Could we also please add the clickhouse user's password to be referenced from a secret clickhouse.config.users.appUserPassword. Like suggested here: #125

I think this is a different use case

[dhable]

Thanks for the contribution. There's a merge conflict, probably around the version, that needs to be resolved. If you revert the Chart.yaml change, it should allow merging in main into your PR branch.

We also would like a changeset in the PR as well. You can create this by running yarn install from the root to install the changeset CLI. Then run yarn changeset and follow the prompts to generate the required files. We can't generate a release without that.

[changeset-bot]

🦋 Changeset detected

Latest commit: b589c94

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
helm-charts	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[dhable]

@namm2 There are some unit tests that are now failing because the rendered template is different. Can you fix up the assertions please?