Remove support for EnableTagOverride in config files

This commit is contained in:
Kyle Havlovitz 2018-05-07 16:19:13 -07:00
parent 6461087c25
commit cc214d45b6
No known key found for this signature in database
GPG Key ID: 8A5E6B173056AD6C
3 changed files with 4 additions and 5 deletions

View File

@ -102,7 +102,6 @@ func Parse(data string, format string) (c Config, err error) {
TranslateKeys(m, map[string]string{
"deregistercriticalserviceafter": "deregister_critical_service_after",
"dockercontainerid": "docker_container_id",
"enabletagoverride": "enable_tag_override",
"scriptargs": "args",
"serviceid": "service_id",
"tlsskipverify": "tls_skip_verify",

View File

@ -1986,7 +1986,7 @@ func TestConfigFlagsAndEdgecases(t *testing.T) {
"service": {
"name": "a",
"port": 80,
"EnableTagOverride": true,
"enable_tag_override": true,
"check": {
"id": "x",
"name": "y",
@ -2001,7 +2001,7 @@ func TestConfigFlagsAndEdgecases(t *testing.T) {
`service = {
name = "a"
port = 80
EnableTagOverride = true
enable_tag_override = true
check = {
id = "x"
name = "y"

View File

@ -48,7 +48,7 @@ unique IDs should be provided.
For Consul 0.9.3 and earlier you need to use `enableTagOverride`. Consul 1.0
supports both `enable_tag_override` and `enableTagOverride` but the latter is
deprecated and will be removed in Consul 1.1.
deprecated and has been removed in Consul 1.1.
The `tags` property is a list of values that are opaque to Consul but
can be used to distinguish between `primary` or `secondary` nodes,
@ -115,7 +115,7 @@ syncs](/docs/internals/anti-entropy.html) for more info.
For Consul 0.9.3 and earlier you need to use `enableTagOverride`. Consul 1.0
supports both `enable_tag_override` and `enableTagOverride` but the latter is
deprecated and will be removed in Consul 1.1.
deprecated and has been removed as of Consul 1.1.
To configure a service, either provide it as a `-config-file` option to
the agent or place it inside the `-config-dir` of the agent. The file