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

Add ability to read playbook from Consul #43

Closed
alexanderdean opened this issue Nov 5, 2015 · 4 comments
Closed

Add ability to read playbook from Consul #43

alexanderdean opened this issue Nov 5, 2015 · 4 comments
Assignees
Milestone

Comments

@alexanderdean
Copy link
Member

No description provided.

@jbeemster
Copy link
Member

Could you expand on how exactly this functionality should work @alexanderdean?

@jbeemster
Copy link
Member

Notes:

@andrioni
Copy link
Contributor

Although using the Consul Golang client is quite easier and probably more stable, a generic REST "playbook provider" would be an incredibly nice thing to have (although it might be borderline scope creep).

@alexanderdean
Copy link
Member Author

Interesting idea @andrioni - feel free to create another ticket for this with how you think it could work!

jbeemster added a commit that referenced this issue Nov 13, 2015
Add ability to read playbook from Consul (closes #43)
Add ability for SQL files to be read from Consul (closes #44)
jbeemster added a commit that referenced this issue Nov 13, 2015
Add ability to read playbook from Consul (closes #43)
Add ability for SQL files to be read from Consul (closes #44)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants