Consul expects prefix rather than keyprefix in watch config #89
Conversation
This file contains 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
|
I don't think so? On type "keyprefix" the key should be "keyprefix" according to the docs: |
|
The 'type' of watch is keyprefix yes, but to specify the actual prefix to watch, the parameter is 'prefix', if you scroll further down to the example config. I've also tested this in a vagrant machine running consul 0.5.0 and confirmed as such. |
|
Ah! I understand. You are right. Thank you! |
solarkennedy
added a commit
that referenced
this pull request
Mar 1, 2015
Consul expects prefix rather than keyprefix in watch config
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Consul expects the 'prefix' parameter rather than 'keyprefix' in watch definitions. Test has been updated too.