etcd non-HA storage backend#259
Merged
armon merged 1 commit intohashicorp:masterfrom May 26, 2015
buth:etcd
Merged
Conversation
Contributor
|
@buth Looks great! Could you just update the documentation on page website/source/docs/config/index.html.md with the new backend and the configuration options? |
Contributor
Author
|
Will do! |
Contributor
Author
|
@armon Added the documentation and rebased! Let me know if you need anything else. |
Contributor
|
@buth Thanks LGTM! |
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This is an implementation of an etcd-based storage backend using the standard client. I've tested it against etcd 2.0.10 with the current version of go-etcd.
I'd like to extend this to implement
HABackend, but it seemed like submitting this as a first step would be a good idea incase I'm on the wrong track.The tests can be run by providing a valid etcd address such as
ETCD_ADDR=http://localhost:4001. At the moment, the backend will sync with the rest of the cluster using only a single address. It's possible to specify an array of machine addresses, but it would involve splitting one of the configuration fields.