Skip to content

Conversation

@holgerjh
Copy link

This PR adds the key tokenSecretKey to the values.yaml. It defines the lookup key used in the token secret defined by tokenSecretName and allows for a more dynamic configuration.

@holgerjh holgerjh requested a review from a team as a code owner November 24, 2025 13:36
@holgerjh
Copy link
Author

Fixes #4019

Copy link
Contributor

@dafydd-t dafydd-t left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR!

  • Can you bump the chart version please?
  • After a merge / rebase & a reorder of tokenSecretKey & tokenSecretName in the README (the linting errors), I think we are good to go 👍

@holgerjh holgerjh force-pushed the feat/expose-token-secret-keyname-in-values branch from 86fb96d to 3d243a2 Compare December 4, 2025 15:15
@holgerjh holgerjh requested a review from dafydd-t December 4, 2025 15:16
@holgerjh
Copy link
Author

holgerjh commented Dec 4, 2025

Thanks for your review. As per semantic version, I bumped the minor version as a new field was added to the API (values.yaml) without breaking backward compatibility. Hope that is ok.

@dafydd-t
Copy link
Contributor

dafydd-t commented Dec 8, 2025

Thanks for your review. As per semantic version, I bumped the minor version as a new field was added to the API (values.yaml) without breaking backward compatibility. Hope that is ok.

This is a newish chart and so we haven't followed semver convention yet, but we may as well start now :) Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants