Ability to set lightswitch value to an environment variable

[Mosnar]

Description

It would be great if there was some way to easily include a lightswitch input that has the ability to be set to a boolean-like environment variable. Admittedly, I'm having a hard time imagining what this UI would look like, but I think it's an important feature when project config makes plugin settings inaccessible. The most obvious use-case is for "dev mode" type lightswitches.

[brandonkelly]

I’m not sure I’m following… can you give me a more concrete example?

[Mosnar]

Sure - here are a couple of examples:

From the AvaTax plugin (note, using a config file to override these settings, ultimately achieving what I'm looking for)

From a Commerce Gateway:

In non-production environments, the gateway uses keys for a sandbox environment, but it only works if developer mode is enabled via the lightswitch.

The work-around is to do what the AvaTax plugin does, which is allow for overriding via a config file. That feels a little inconsistent/antiquated to me, since we have the ability to enter environment variables all over the control panel now.

[nettum]

This could also be useful for other fieldtypes.
E.g. if you want different email settings between envs in craft and using project config / allowAdminChanges.
All text fields can be set to env variables in the UI, but not the checkbox (useAuthentication) an the dropdowns (transport and encryption).

[brandonkelly]

Noticed Zapier has a pretty elegant solution for this sort of thing. In their case you might want to pull in a boolean value from a prior step in the zap, which is sortof like needing to pull in an environment variable.

We’re going to get this into v4.

[brandonkelly]

Just resolved this a little ahead of schedule, for the next Craft 3 release 🚀

See details at #10111

[brandonkelly]

Craft 3.7.22 is out now with those changes.