Go to file
Iryna Shustava 5eb8ee0cac
sdk: Use /v1/status/leader endpoint when starting a test server (#8192)
Switch from /v1/agent/self to /v1/status/leader when checking if the test server has come up successfully in the waitForAPI function.

Previously, the test server was relying (probably not intentionally) on the default value of the acl_enforce_version_8 in the TestConfig, which was false. So if you create a test server and enabled ACLs, they would not be enforced and the server would be able to come up pretty quickly because /v1/agent/self would return a 200 status pretty much as soon as the agent is running and most likely before leader election is finished.

Now that we have removed acl_enforce_version_8 property (equivalent to being true by default) if you've created a test server with ACLs enabled, it will need to wait for leader election and for ACLs to be initialized before it'll get a successful response from the /v1/agent/self.

Note: With this change, waitForAPI function no longer requires a 200 response status from the v1/status/leader endpoint. This is because in some tests, namely TestAPI_AgentLeave, we are only running clients, and this endpoint returns a 500 status.
2020-07-07 14:25:17 -07:00
.circleci Add Algolia indexing to CI 2020-06-29 12:14:43 -04:00
.github
acl Merge pull request #8035 from hashicorp/feature/auto-config/server-rpc 2020-06-17 16:07:25 -04:00
agent Append port number to ingress host domain (#8190) 2020-07-07 10:43:04 -05:00
api api/agent: enable setting SuccessBeforePassing and FailuresBeforeCritical in API (#7949) 2020-06-29 14:52:35 +02:00
bench
build-support Implement the insecure version of the Cluster.AutoConfig RPC endpoint 2020-06-17 11:25:29 -04:00
command cli: Output message on success when writing/deleting entries (#7806) 2020-06-29 15:47:40 -05:00
connect Implement Client Agent Auto Config 2020-06-17 16:49:46 -04:00
contributing
demo
internal/go-sso Merge pull request #8035 from hashicorp/feature/auto-config/server-rpc 2020-06-17 16:07:25 -04:00
ipaddr
lib Merge pull request #8176 from hashicorp/dnephin/add-linter-unparam-1 2020-06-25 15:34:48 -04:00
logging Implement Client Agent Auto Config 2020-06-17 16:49:46 -04:00
sdk sdk: Use /v1/status/leader endpoint when starting a test server (#8192) 2020-07-07 14:25:17 -07:00
sentinel
service_os
snapshot
terraform
test Append port number to ingress host domain (#8190) 2020-07-07 10:43:04 -05:00
testrpc
tlsutil Add an AutoEncrypt “integration” test 2020-06-30 15:23:29 -04:00
types
ui-v2 ui: Remove jQuery from the production build (#8088) 2020-07-07 19:58:46 +01:00
vendor Upgrade go-connlimit to v0.3.0 / return http 429 on too many connections (#8221) 2020-07-03 09:25:07 +02:00
version
website learn -> tutorials in subnav 2020-07-06 18:44:30 -04:00
.dockerignore
.gitattributes
.gitignore
.golangci.yml Remove unused return values 2020-06-24 13:00:15 -04:00
.hashibot.hcl
CHANGELOG.md Update CHANGELOG.md 2020-07-07 10:45:25 -05:00
GNUmakefile
INTERNALS.md
LICENSE
NOTICE.md
README.md
Vagrantfile
codecov.yml
go.mod Upgrade go-connlimit to v0.3.0 / return http 429 on too many connections (#8221) 2020-07-03 09:25:07 +02:00
go.sum Upgrade go-connlimit to v0.3.0 / return http 429 on too many connections (#8221) 2020-07-03 09:25:07 +02:00
main.go clean cli.Run error message (#8191) 2020-06-30 13:12:29 +02:00
main_test.go
package-lock.json Add Algolia indexing to CI 2020-06-29 12:14:43 -04:00

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.