0b9ff5c2b9
This has an explcit unit test already which somehow passes at least some of the time. I suspect it passes because under some conditions the actual KV delete fails and returns non-zero as well as printing the warning which is what is being checked for in the test. For some reason despite working for quite some time like this, I now have a branch in which this test fails consistently. It may be a timing/env issue where another process running an agent causes the delete to be successful so the command returns a 0 by chance. Either way this is clearly wrong and fixing it stops the test being flaky in my branch. |
||
---|---|---|
.github/ISSUE_TEMPLATE | ||
acl | ||
agent | ||
api | ||
bench | ||
command | ||
demo | ||
ipaddr | ||
lib | ||
logger | ||
scripts | ||
sentinel | ||
snapshot | ||
terraform | ||
test | ||
testrpc | ||
testutil | ||
tlsutil | ||
types | ||
ui | ||
ui-v2 | ||
vendor | ||
version | ||
watch | ||
website | ||
.gitattributes | ||
.gitignore | ||
.travis.yml | ||
CHANGELOG.md | ||
GNUmakefile | ||
INTERNALS.md | ||
LICENSE | ||
main.go | ||
main_test.go | ||
README.md | ||
Vagrantfile |
Consul
- Website: https://www.consul.io
- Chat: Gitter
- Mailing list: Google Groups
Consul is a tool for service discovery and configuration. Consul is distributed, highly available, and extremely scalable.
Consul provides several key features:
-
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.
-
Multi-Datacenter - Consul is built to be datacenter aware, and can support any number of regions without complex configuration.
Consul runs on Linux, Mac OS X, FreeBSD, Solaris, and Windows. A commercial version called Consul Enterprise is also available.
Quick Start
An extensive quick start is viewable on the Consul website:
https://www.consul.io/intro/getting-started/install.html
Documentation
Full, comprehensive documentation is viewable on the Consul website:
Developing Consul
If you wish to work on Consul itself, you'll first need Go installed (version 1.9+ is required). Make sure you have Go properly installed, including setting up your GOPATH.
Next, clone this repository into $GOPATH/src/github.com/hashicorp/consul
and
then just type make
. In a few moments, you'll have a working consul
executable:
$ make
...
$ bin/consul
...
Note: make
will build all os/architecture combinations. Set the environment variable CONSUL_DEV=1
to build it just for your local machine's os/architecture, or use make dev
.
Note: make
will also place a copy of the binary in the first part of your $GOPATH
.
You can run tests by typing make test
. The test suite may fail if
over-parallelized, so if you are seeing stochastic failures try
GOTEST_FLAGS="-p 2 -parallel 2" make test
.
If you make any changes to the code, run make format
in order to automatically
format the code according to Go standards.
Vendoring
Consul currently uses govendor for
vendoring and vendorfmt for formatting
vendor.json
to a more merge-friendly "one line per package" format.