You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Boot requires a number of environment variables, e.g. BOOT_WATCHERS_DISABLE, to be 1 or yes. This is arbitrary and contrary to expectation--we recently ran into an issue where BOOT_WATCHERS_DISABLE wasn't working because we had set it to true, a much more common and conventional value.
These environment variables should accept any truthy value, e.g. true, and reject only some values, e.g. false.
I agree there is a problem with that there, but we should follow some convention, not pick arbitrary things and || them together.
For instance one could pick the following convention: when the variable is set it means the "feature" is enabled, no matter what value. But this is only one possible solution.
Probably the picked convention should be really clear in the env var documentation.
Boot Bug Report
Platform details
Platform (macOS, Linux, Windows):
Darwin C02RW05YFVH6 15.6.0
JRE/JDK version (
java -version
):Boot details
Description
Boot requires a number of environment variables, e.g.
BOOT_WATCHERS_DISABLE
, to be1
oryes
. This is arbitrary and contrary to expectation--we recently ran into an issue whereBOOT_WATCHERS_DISABLE
wasn't working because we had set it totrue
, a much more common and conventional value.These environment variables should accept any truthy value, e.g.
true
, and reject only some values, e.g.false
.Steps to reproduce
BOOT_WATCHERS_DISABLE
totrue
incircle.yml
The text was updated successfully, but these errors were encountered: