Consul is a distributed, highly available, and data center aware solution to connect and configure applications across dynamic, distributed infrastructure.
After release 1.2.0, the watch cannot be triggered at all, More info you can find under following link, https://github.com/hashicorp/consul/issues/4076
I don't have permission to re-open the old ticket, because it was not closed by me.
you cannot re-open your own issues if a repo collaborator closed them
The problem is that after upgrade to new version v1.2.0 the watch cannot be triggered any more
Overview of the Issue
After release 1.2.0, the watch cannot be triggered at all, More info you can find under following link, https://github.com/hashicorp/consul/issues/4076 I don't have permission to re-open the old ticket, because it was not closed by me.
The problem is that after upgrade to new version v1.2.0 the watch cannot be triggered any more
Reproduction Steps
Steps to reproduce this issue, eg:
Consul info for both Client and Server
Client
Server
Operating system and Environment details
Log Fragments