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

Environment vars #7

Closed
heyoka opened this issue Aug 17, 2020 · 2 comments
Closed

Environment vars #7

heyoka opened this issue Aug 17, 2020 · 2 comments

Comments

@heyoka
Copy link

heyoka commented Aug 17, 2020

I would like to warm up an old issue from the original basho cuttlefish repository:
Environment Variables
Is there any change for such a feature ?
I woud need this for different scenarios where config via Environment vars is mandatory.

Thank you.

@michaelklishin
Copy link
Collaborator

Environment variables are "arbitrarily typed", unvalidated inputs so using them should be a last resort measure. However, I can see how this can be useful in a narrow number of cases.

If Cuttlefish expanded such variables before performing validation and would take the key type into account when parsing the values, it might work well. Rendering values verbatim is also an option.

We need someone interested to put together a specific proposal as to how exactly such environment variable support would work. For example, we can add a built-in function instead of a special syntax. We need to decide what to do with the implicit typing of raw env variable values.

@heyoka would you be up for putting together a specific proposal with some examples that address the typing question above?

@michaelklishin
Copy link
Collaborator

Closing due to the lack of activity (and interest in env variable support from some of the heaviest users of Cuttlefish today).

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

No branches or pull requests

2 participants