Go to file
Daniel Nephin d406f78c5c ca: remove unused provider.ActiveRoot call
In the previous commit the single use of this storedRoot was removed.

In this commit the original objective is completed. The
Provider.ActiveRoot is being removed because

1. the secondary should get the active root from the Consul primary DC,
   not the provider, so that secondary DCs do not need to communicate
   with a provider instance in a different DC.
2. so that the Provider.ActiveRoot interface can be changed without
   impacting other code paths.
2022-01-06 16:56:48 -05:00
.changelog Fix Windows logging to files (#11960) 2022-01-06 16:07:09 -05:00
.circleci website: fix algolia indexing (#11413) 2021-12-15 08:30:46 -06:00
.github removing markdown file for consul docs day issue 2022-01-03 11:06:09 -07:00
.release Removing test branch 2021-12-14 18:19:14 -08:00
acl
agent ca: remove unused provider.ActiveRoot call 2022-01-06 16:56:48 -05:00
api add path escape and unescape to path params 2022-01-03 08:18:32 -08:00
bench
build-support
command cli: use file mode 0600 when saving a snapshot 2022-01-05 17:51:03 -05:00
connect
contributing
demo
docs
grafana
internal
ipaddr
lib
logging Fix Windows logging to files (#11960) 2022-01-06 16:07:09 -05:00
proto
sdk
sentinel
service_os
snapshot
terraform
test Fix integration test with updated file perms (#11916) 2021-12-23 19:00:02 -05:00
testrpc ca: remove unused provider.ActiveRoot call 2022-01-06 16:56:48 -05:00
tlsutil
types
ui ui: Add selective no-console eslint rule (#11938) 2022-01-05 16:56:26 +00:00
version
website docs: Redirect mesh-gateway page to new location 2022-01-06 13:35:11 -08:00
.dockerignore
.gitattributes
.gitignore
.golangci.yml
CHANGELOG.md Resolve conflicts 2021-12-15 09:14:15 -08:00
Dockerfile
GNUmakefile
INTERNALS.md
LICENSE
NOTICE.md
README.md
Vagrantfile
codecov.yml
go.mod upgrade raft to v1.3.3 (#11958) 2022-01-06 14:09:13 -05:00
go.sum upgrade raft to v1.3.3 (#11958) 2022-01-06 14:09:13 -05:00
main.go
main_test.go

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, macOS, FreeBSD, Solaris, and Windows and includes an optional browser based UI. 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. For contributions specifically to the browser based UI, please refer to the UI's README.md for guidance.