-
Notifications
You must be signed in to change notification settings - Fork 917
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
support 'enableTagOverride' for consul backend #347
Comments
+1, required to properly deal with master/slave status on services (the master/slave tag is set after a leader election) |
I'm thinking maybe it'd be ok even if 'enableTagOverride' was always set to true. Should be a 1~2 line PR. Will cook one up soon. |
+1 |
+1 |
3 similar comments
+1 |
+1 |
+1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
consul 0.6 landed with 'enableTagOverride' which disables 'anti-entropy' feature for each service being registered. This lets external agents to modify tags for already registered services.
Since this has been merged into consul go api,
It'd be great registrator also supported this feature.
I'm thinking maybe, something like
SERVER_ENABLETAGOVERRIDE=true
env ?The text was updated successfully, but these errors were encountered: