Skip to content
This repository was archived by the owner on Apr 15, 2024. It is now read-only.

Use standard consul environment variables to override configuration#74

Merged
cablehead merged 7 commits into
python-consul:masterfrom
amayausky:using-environment-vars
Feb 7, 2016
Merged

Use standard consul environment variables to override configuration#74
cablehead merged 7 commits into
python-consul:masterfrom
amayausky:using-environment-vars

Conversation

@amayausky
Copy link
Copy Markdown
Contributor

Other Hashicorp tools, envconsul and consul-template, use this set of environment variables to provide configuration for themselves and other consul tools they're integrated with. I've implemented them as overrides to what is normally passed in to the constructor. That seems to make sense since an application can be configured to use the default host/port but then be overridden by providing CONSUL_HTTP_ADDR.

@cablehead
Copy link
Copy Markdown
Collaborator

Sorry for the delay in getting to this. This looks great. Thanks @amayausky!

cablehead added a commit that referenced this pull request Feb 7, 2016
Use standard consul environment variables to override configuration
@cablehead cablehead merged commit 83cfde3 into python-consul:master Feb 7, 2016
@cablehead
Copy link
Copy Markdown
Collaborator

What do you think about adding documentation for these? Perhaps in docs/index.rst, between the client section and the tools section?

@cablehead
Copy link
Copy Markdown
Collaborator

Uploaded to pypi as v0.6.0

@amayausky amayausky deleted the using-environment-vars branch March 28, 2016 03:18
mbrulatout referenced this pull request in criteo/py-consul Aug 28, 2023
Use standard consul environment variables to override configuration
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants