You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently it would appear that when registering external services inside the default admin partition and in any namespace, Consul ESM works as expected.
However, when running Consul ESM against a specific admin partition with a token tied to a specific partition, it will not pick up the external nodes and services and they will sit forever.
I am also guessing because we are using go module consul 1.14.3, we are seeing some issues with this so this PR might be required for review/merging to fix this? #253
This was setup using Hashicorp docs
The text was updated successfully, but these errors were encountered:
Currently it would appear that when registering external services inside the default admin partition and in any namespace, Consul ESM works as expected.
However, when running Consul ESM against a specific admin partition with a token tied to a specific partition, it will not pick up the external nodes and services and they will sit forever.
I am also guessing because we are using go module consul 1.14.3, we are seeing some issues with this so this PR might be required for review/merging to fix this?
#253
This was setup using Hashicorp docs
The text was updated successfully, but these errors were encountered: