-envFile option to read variables from within container at runtime #678
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I need to change Consul service description from inside container by custom application logic. This patch allow this by specifying
-envFile
option to registrator which is the file path inside containers. Registrator try reads this file at runtime from each container instance and use as another source of configuration like Labels or ENV but with highest priority.Examples:
File /tmp/dynamic_envs inside test_container
Registrator launch:
Dynamic changes:
After refresh interval(10s) new metadata with name meta and value 123 appear in already registered consul service.
What do you think?