When using the default: '%env()%' syntax the environment variable will accurately display the correct (bool) value.
However, if wanting to add the default: false as a security measure, then allowing env: attribute to dynamically override the value this won't work. The docs mention that given the ENV var name, this should be dynamically pulled at runtime.
The purpose is to want to harden the state of new feature deployments until EAP users verify the integrity of the canary release.
I will need to program a custom extension for the constraint: attribute in the meantime to pull from a feature table.
First off, I want to say (GREAT BUNDLE!)
When using the
default: '%env()%'syntax the environment variable will accurately display the correct (bool) value.However, if wanting to add the
default: falseas a security measure, then allowingenv:attribute to dynamically override the value this won't work. The docs mention that given the ENV var name, this should be dynamically pulled at runtime.The purpose is to want to harden the state of new feature deployments until EAP users verify the integrity of the canary release.
I will need to program a custom extension for the
constraint:attribute in the meantime to pull from a feature table.ie: something like:
constraint: feature_flag == SOME_FEATURE_FLAG_NAMEThis will allow live changes without re-deployment.
I would be happy to make a pull request if pointed in the right direction.
Could potentially add an agnostic function that allows end users of this bundle to point to a connection & table.