Conversation
Wire the application-level reCAPTCHA opt-outs into Kubernetes so local development can run without external CAPTCHA credentials. The applications retain enabled defaults; these chart settings provide an explicit way to disable them and omit references to CAPTCHA secrets that need not exist locally. Expose app.recaptcha.enabled for the API, ui.recaptchaEnabled for the UI, and mw.recaptcha.enabled for MediaWiki, all defaulting to true. Pass the corresponding RECAPTCHA_ENABLED or MW_RECAPTCHA_ENABLED environment variable and conditionally omit reCAPTCHA keys and secret references. The opt-out requires images containing the corresponding application support: API: wbstack/api#1278 Bypass validation only when explicitly disabled and APP_ENV=local. UI: wbstack/ui#1222 Skip requesting a reCAPTCHA token when disabled; configure the API opt-out separately. MediaWiki: wbstack/mediawiki#564 Honor MW_RECAPTCHA_ENABLED=no while preserving per-wiki QuestyCaptcha settings. This change does not update application image tags or disable reCAPTCHA by default.
This branch has not been deployed
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
1 participant
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.
Wire the application-level reCAPTCHA opt-outs into Kubernetes so local development can run without external CAPTCHA credentials. The applications retain enabled defaults;
these chart settings provide an explicit way to disable them and omit references to CAPTCHA secrets that need not exist locally.
Expose app.recaptcha.enabled for the API,
ui.recaptchaEnabled for the UI,
and mw.recaptcha.enabled for MediaWiki,
all defaulting to true.
Pass the corresponding RECAPTCHA_ENABLED or MW_RECAPTCHA_ENABLED environment variable and conditionally omit reCAPTCHA keys and secret references.
The opt-out requires images containing the corresponding application support:
API: wbstack/api#1278
Bypass validation only when explicitly disabled and APP_ENV=local.
UI: wbstack/ui#1222
Skip requesting a reCAPTCHA token when disabled; configure the API opt-out separately.
MediaWiki: wbstack/mediawiki#564 Honor MW_RECAPTCHA_ENABLED=no while preserving per-wiki QuestyCaptcha settings.
This change does not update application image tags or disable reCAPTCHA by default.