Go to file
Riddhi Shah e5f1d8dce4
Add support for merge-central-config query param (#13001)
Adds a new query param merge-central-config for use with the below endpoints:

/catalog/service/:service
/catalog/connect/:service
/health/service/:service
/health/connect/:service

If set on the request, the response will include a fully resolved service definition which is merged with the proxy-defaults/global and service-defaults/:service config entries (on-demand style). This is useful to view the full service definition for a mesh service (connect-proxy kind or gateway kind) which might not be merged before being written into the catalog (example: in case of services in the agentless model).
2022-05-25 13:20:17 -07:00
.changelog Add support for merge-central-config query param (#13001) 2022-05-25 13:20:17 -07:00
.circleci api: ensure peering API endpoints do not use protobufs (#13204) 2022-05-25 13:43:35 -05:00
.github
.release
acl
agent Add support for merge-central-config query param (#13001) 2022-05-25 13:20:17 -07:00
api Add support for merge-central-config query param (#13001) 2022-05-25 13:20:17 -07:00
bench
build-support api: ensure peering API endpoints do not use protobufs (#13204) 2022-05-25 13:43:35 -05:00
command
connect
contributing
docs
grafana
internal
ipaddr
lib
logging Add support for merge-central-config query param (#13001) 2022-05-25 13:20:17 -07:00
proto api: ensure peering API endpoints do not use protobufs (#13204) 2022-05-25 13:43:35 -05:00
proto-public
sdk
sentinel
service_os
snapshot
test
testrpc
tlsutil
types
ui
version update main to reflect 1.13.0-dev (#13192) 2022-05-25 09:06:36 -07:00
website update docs for single-dc-multi-k8s install (#13008) 2022-05-25 11:34:56 -07:00
.dockerignore
.gitattributes
.gitignore
.golangci.yml
CHANGELOG.md Update CHANGELOG to mention removal of Envoy 1.17.4 and 1.18.6 (#13207) 2022-05-25 08:57:01 -07:00
Dockerfile
GNUmakefile api: ensure peering API endpoints do not use protobufs (#13204) 2022-05-25 13:43:35 -05:00
LICENSE
NOTICE.md
README.md
Vagrantfile
fixup_acl_move.sh
go.mod
go.sum
main.go

README.md

Consul logo Consul

Docker Pulls Go Report Card

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.