Go to file
Pierre Souchay 54f9f247f8
Consul Service meta wrongly computes and exposes non_voter meta (#8731)
* Consul Service meta wrongly computes and exposes non_voter meta

In Serf Tags, entreprise members being non-voters use the tag
`nonvoter=1`, not `non_voter = false`, so non-voters in members
were wrongly displayed as voter.

Demonstration:

```
consul members -detailed|grep voter
consul20-hk5 10.200.100.110:8301   alive   acls=1,build=1.8.4+ent,dc=hk5,expect=3,ft_fs=1,ft_ns=1,id=xxxxxxxx-5629-08f2-3a79-10a1ab3849d5,nonvoter=1,port=8300,raft_vsn=3,role=consul,segment=<all>,use_tls=1,vsn=2,vsn_max=3,vsn_min=2,wan_join_port=8302
```

* Added changelog

* Added changelog entry
2020-10-09 17:18:24 -04:00
.changelog Consul Service meta wrongly computes and exposes non_voter meta (#8731) 2020-10-09 17:18:24 -04:00
.circleci [skip ci] ci: fix trigger-oss-merge yaml spacing (#8916) 2020-10-09 16:12:54 -04:00
.github Docs: Nia/docs tech preview (#8908) 2020-10-09 13:37:20 -05:00
acl
agent Consul Service meta wrongly computes and exposes non_voter meta (#8731) 2020-10-09 17:18:24 -04:00
api upstream some differences from enterprise (#8902) 2020-10-09 09:42:53 -05:00
bench
build-support upstream some differences from enterprise (#8902) 2020-10-09 09:42:53 -05:00
command Enhance the output of consul snapshot inspect (#8787) 2020-10-09 14:57:29 -05:00
connect connect: intentions are now managed as a new config entry kind "service-intentions" (#8834) 2020-10-06 13:24:05 -05:00
contributing config: add field for enabling streaming RPC endpoint 2020-10-08 12:11:20 -04:00
demo
internal/go-sso
ipaddr
lib Merge pull request #8877 from hashicorp/mkcp/telemetry/consul.api.http 2020-10-08 13:22:37 -07:00
logging Add /v1/internal/ui/metrics-proxy API endpoint that proxies to a configured metrics provider backend. 2020-10-08 17:32:29 +01:00
proto streaming: store services with a unique ID that includes namespace 2020-10-06 16:54:56 -04:00
sdk connect: intentions are now managed as a new config entry kind "service-intentions" (#8834) 2020-10-06 13:24:05 -05:00
sentinel
service_os
snapshot Enhance the output of consul snapshot inspect (#8787) 2020-10-09 14:57:29 -05:00
terraform
test connect: support defining intentions using layer 7 criteria (#8839) 2020-10-06 17:09:13 -05:00
testrpc add testrpc.WaitForServiceIntentions to help unflake tests that manipulate intentions (#8867) 2020-10-07 14:20:25 -05:00
tlsutil
types
ui-v2 ui: Make the topology cards into links (#8911) 2020-10-09 16:57:08 -04:00
vendor vendor: Update github.com/hashicorp/yamux 2020-10-09 05:05:46 -07:00
version
website Update service-defaults.mdx (#8780) 2020-10-09 13:43:52 -07:00
.dockerignore
.gitattributes
.gitignore
.golangci.yml
.hashibot.hcl
CHANGELOG.md Update CHANGELOG.md 2020-10-06 16:27:38 -04:00
GNUmakefile Update CI for leader renew CA test using Vault 2020-10-09 05:48:15 -07:00
INTERNALS.md
LICENSE
NOTICE.md
README.md
Vagrantfile
codecov.yml
go.mod vendor: Update github.com/hashicorp/yamux 2020-10-09 05:05:46 -07:00
go.sum vendor: Update github.com/hashicorp/yamux 2020-10-09 05:05:46 -07:00
main.go
main_test.go
package-lock.json

README.md

Consul CircleCI Discuss

Consul is a distributed, highly available, and data center aware solution to connect and configure applications across dynamic, distributed infrastructure.

Consul provides several key features:

  • Multi-Datacenter - Consul is built to be datacenter aware, and can support any number of regions without complex configuration.

  • Service Mesh/Service Segmentation - Consul Connect enables secure service-to-service communication with automatic TLS encryption and identity-based authorization. Applications can use sidecar proxies in a service mesh configuration to establish TLS connections for inbound and outbound connections without being aware of Connect at all.

  • Service Discovery - Consul makes it simple for services to register themselves and to discover other services via a DNS or HTTP interface. External services such as SaaS providers can be registered as well.

  • Health Checking - Health Checking enables Consul to quickly alert operators about any issues in a cluster. The integration with service discovery prevents routing traffic to unhealthy hosts and enables service level circuit breakers.

  • Key/Value Storage - A flexible key/value store enables storing dynamic configuration, feature flagging, coordination, leader election and more. The simple HTTP API makes it easy to use anywhere.

Consul runs on Linux, Mac OS X, FreeBSD, Solaris, and Windows. A commercial version called Consul Enterprise is also available.

Please note: We take Consul's security and our users' trust very seriously. If you believe you have found a security issue in Consul, please responsibly disclose by contacting us at security@hashicorp.com.

Quick Start

A few quick start guides are available on the Consul website:

Documentation

Full, comprehensive documentation is available on the Consul website:

https://www.consul.io/docs

Contributing

Thank you for your interest in contributing! Please refer to CONTRIBUTING.md for guidance.