Fix for name/handling of the group auth secret name helper

[vctrstrm]

Template for group auth secret is misspelled as .Values.auth.groupAuthSecret when it should be .Values.auth.groupsAuthSecret (the value name used in all other templates)

Additionally, since the the value of ".Values.auth.groupsAuthSecret" is meant to be a secret name, I removed truncation/trimming as the name should be taken verbatim

Without this fix, the workaround is to declare duplicate env vars for both:

auth:
  # [BUG WORKAROUND] - template references secret with two different names, hence duplication
  groupAuthSecret: trino-group-auth
  groupsAuthSecret: trino-group-auth
  passwordAuthSecret: trino-password-auth

[cla-bot]

Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to [email protected]. Photos, scans, or digitally-signed PDF files are all suitable. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla

[vctrstrm]

signed cla submitted 👍

[cla-bot]

Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to [email protected]. Photos, scans, or digitally-signed PDF files are all suitable. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla

[cla-bot]

Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to [email protected]. Photos, scans, or digitally-signed PDF files are all suitable. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla

[vctrstrm]

@nineinchnick it seems CLA approval process is a bit stuck. Any idea if there's someone we could tap on the shoulder to help approve it? Would love to contribute more to the project :)

[nineinchnick]

@martint handles the CLA every few weeks. The file was updated 3 weeks ago, so I'd expect another batch to be done soon.

[vctrstrm]

cla list updated (trying to see if this will trigger re-check)

[nineinchnick]

@cla-bot check

[cla-bot]

The cla-bot has been summoned, and re-checked this pull request!