Skip to content

Fixed Boolean logic for HCAPTCHA_SITE_KEY in _env.tpl#35

Open
pwhack wants to merge 4 commits intomastodon:mainfrom
pwhack:main
Open

Fixed Boolean logic for HCAPTCHA_SITE_KEY in _env.tpl#35
pwhack wants to merge 4 commits intomastodon:mainfrom
pwhack:main

Conversation

@pwhack
Copy link

@pwhack pwhack commented Feb 8, 2026

Hi,

Without this PR, someone specifying mastodon.hcaptcha.enabled: false in their values.yaml file will end up with HCAPTCHA_SITE_KEY: in their mastodon-env and mastodon-env-predeploy ConfigMap objects. Tools like Argo CD won't be able to apply this null value and continually show the application as out of sync.

I believe the intention in _env.tpl is for the user to be able to fully disable hcaptcha and not have lingering keys or values related to it. This PR fixes the intention by properly looking for a Boolean value rather than trying to cast it to a string object, with unclear behavior.

@timetinytim
Copy link
Contributor

Thank you for catching this!

I'll approve once it starts passing the checks (you need to update the Chart.yaml file)

@pwhack
Copy link
Author

pwhack commented Feb 13, 2026

Whoops, sorry about that, I should have thought about that. I've bumped the patch column of the version string. That appears to be what the test was looking for. Need anything else?

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.

BUG: charts/mastodon: erroneous value check in values is not disabling hcaptcha

2 participants