teller
teller copied to clipboard
Provider request - parent_process_env
New Provider Request
Instead of carry_env
option, we should have a parent_process_env
provider. So we can selectively load up parent process env vars as needed. It would also allow renaming the field/variable as needed.
It's very useful if we need to run a docker container:
$ docker run --rm -it --env-file <(teller env) alpine sh
// Should also will populate the following for various use-cases:
$ teller show
$ teller json
$ teller yaml
providers:
parent_process_env:
env:
GIT_SHA:
Details
- Name: parent_process_env
- Modes: read
Hey @kevbook, just to make sure that i understand your case, Your suggestion is allow Teller to read parent environment variable like this example:
export SECRET-KEY=<secret value>
and the .teller.yaml
file config will look like:
providers:
parent_process_env:
env:
telelr-secret-key: SECRET-KEY
@kaplanelad Yes.
ps. We should also get rid of the carry_env
option, seems very opinioned on how it handles $HOME
, and exposes the entire set of keys from the parent.
@kevbook We discussed on your feature internally, and it looks like a great idea. Do you want to create a pull request with the new provider? I can assist you if you need to
Absolutely, I’ll take a stab this weekend. What do you want to call it, I’m open to whatever you suggest
Amazing, you can take a look k in this doc, which Champlain how to add a new provider. I'm available for open questions that you have and also in slack (I'll give you the name later).
I think proccess_env
/env_vars
will be good.
@kevbook the provider release in version 1.5.5. thanks for your contribution