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

Allow customization of environment variable names #108

Open
averymd opened this issue Apr 27, 2024 · 0 comments
Open

Allow customization of environment variable names #108

averymd opened this issue Apr 27, 2024 · 0 comments

Comments

@averymd
Copy link

averymd commented Apr 27, 2024

Summary

It would be nice to be able to change the environment variable names from OP_CONNECT_HOST and/or OP_CONNECT_TOKEN to variables of our choosing when calling new_client_from_environment(). TOKEN is the more important one, since the host can be passed in already.

Use cases

My primary use case is having a single VM that runs multiple applications (not in docker) that need different tokens.

Is there a workaround to accomplish this today?

There are other ways to scope environment env variables. For instance, I could set them in the processes' systemd service files, although then I shift to the problem to having to manage the secrets in those files in my repository and during deployment.

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

1 participant