Skip to content
This repository has been archived by the owner on Aug 22, 2023. It is now read-only.

env attribute isn't pulling from .env.* files #104

Open
danbadds38 opened this issue Apr 24, 2023 · 0 comments
Open

env attribute isn't pulling from .env.* files #104

danbadds38 opened this issue Apr 24, 2023 · 0 comments

Comments

@danbadds38
Copy link

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: 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.

ie: something like: constraint: feature_flag == SOME_FEATURE_FLAG_NAME

This 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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant