Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature]: Using unleash as env resolver %env(unleash:feature_name)% #61

Open
1 task done
ybenhssaien opened this issue Mar 1, 2024 · 0 comments
Open
1 task done
Assignees

Comments

@ybenhssaien
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Describe the new feature

Hello all,

We have been using unleash in a professional project based in an hexagonal architecture where we separate and put every app configuration in yaml param file and use those files to configure features toggles to enable/disable features using unleash (this bundle), to ensure using the same methodology before unleash I suggested and developed an Env processor to replace Env variables by unleash using yaml syntaxe which is a good way to create one parameter connected to unleash variable and use it everywhere in the app.

%env(unleash:feature_name)%

to make a default value we just need to declare a default value for the env

 parameters:
     %env(unleash:feature_name)%: false

I suggest to integrate this possibility into this bundle while we can enable/disable this feature by extension parameter.

You may take a look on my created pull request (marked draft) : #60

Is your feature request related to a problem? (optional)

Add a new possibility to use unleash from yaml/xml configuration

Describe alternatives you've considered (optional)

No response

Additional context (optional)

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Support rotation
Development

No branches or pull requests

2 participants