Skip to content

Add hooks for remote configuration and live updates #22

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

Closed
rosejn opened this issue May 14, 2015 · 3 comments
Closed

Add hooks for remote configuration and live updates #22

rosejn opened this issue May 14, 2015 · 3 comments

Comments

@rosejn
Copy link

rosejn commented May 14, 2015

We are going to use consul (https://consul.io/) as a service discovery and configuration server as well as vault (https://vaultproject.io/) for secure credentials, and it would be ideal to integrate them into our standard nomad config usage.

How about adding a means of prepending additional phases in the preference ordering for reading config values? Maybe this is just handing nomad functions that will return a map? This way we can check consul and/or vault for config values, and then fall back to the config file.

It would also be great to support live config updates. Consul uses long-polling to allow for real-time updating of config values. (I guess nomad could do the same for local files with a watcher too.) Maybe add a listen function?

(nomad/listen CONFIG [:sql :host] sql-host-change-callback)

What do you think?

@jarohen
Copy link
Owner

jarohen commented May 19, 2015

Hi Jeff, sorry for the tardy response. Will have a think about the best way to incorporate this into Nomad - it might be that this is a layer above Nomad, and that we just have to make sure that Nomad's extensible enough to be able to cope with it?

James

@rosejn
Copy link
Author

rosejn commented May 20, 2015

Hey,

  After digging into this more we are going to use environment vars instead of config files, so no changes needed for us.  Thanks for getting back though.

On Tue, May 19, 2015 at 1:48 PM, James Henderson [email protected]
wrote:

Hi Jeff, sorry for the tardy response. Will have a think about the best way to incorporate this into Nomad - it might be that this is a layer above Nomad, and that we just have to make sure that Nomad's extensible enough to be one with it?

James

Reply to this email directly or view it on GitHub:
#22 (comment)

@jarohen
Copy link
Owner

jarohen commented May 20, 2015

No worries, thanks Jeff :)

@jarohen jarohen closed this as completed May 20, 2015
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