20 Commits (744d4675409b717d11c6ba760c071176513b664b)

Author	SHA1	Message	Date
R.B. Boyer	80b1165976	fix use of hclog logger (#7264)	5 years ago
Chris Piraino	401221de58	Allow users to configure either unstructured or JSON logging (#7130) ... * hclog Allow users to choose between unstructured and JSON logging	5 years ago
Hans Hasselberg	33a7df3330	tls: auto_encrypt enables automatic RPC cert provisioning for consul clients (#5597)	5 years ago
Matt Keeler	222afeae4c	Move the watch package into the api module (#5664) ... * Move the watch package into the api module It was already just a thin wrapper around the API anyways. The biggest change was to the testing. Instead of using a test agent directly from the agent package it now uses the binary on the PATH just like the other API tests. The other big changes were to fix up the connect based watch tests so that we didn’t need to pull in the connect package (and therefore all of Consul)	6 years ago
R.B. Boyer	f4a3b9d518	fix typos reported by golangci-lint:misspell (#5434)	6 years ago
Matt Keeler	89ba649252	Connect: Verify the leaf cert to determine its readiness. (#4540) ... This improves the checking so that if a certificate were to expire or the roots changed then we will go into a non-ready state. This parses the x509 certificates from the TLS certificate when the leaf is set. The readyCh will be closed whenever a parseable certificate is set and the ca roots are set. This does not mean that the certificate is valid but that it has been setup and is generally valid. The Ready function will now do x509 certificate verification which will in addition to verifying the signatures with the installed CA roots will also verify the certificate isn't expired or not set to become valid in the future. The correct way to use these functions is to wait for the ReadyWait chan to be closed and then periodically check the readiness to determine if the certificate is currently useable.	6 years ago
Paul Banks	af2901130d	Implement missing HTTP host to ConsulResolver func for Connect SDK.	6 years ago
Paul Banks	c08b6f6fec	Add accessor and helpers to SDK for fetching self-name and client service ID	7 years ago
Paul Banks	541cbae5f5	More misc comment cleanup	7 years ago
Paul Banks	0824d1df5f	Misc comment cleanups	7 years ago
Mitchell Hashimoto	8c713e6104	connect/proxy: don't require proxy ID	7 years ago
Paul Banks	e0e12e165b	TLS watching integrated into Service with some basic tests. ... There are also a lot of small bug fixes found when testing lots of things end-to-end for the first time and some cleanup now it's integrated with real CA code.	7 years ago
Paul Banks	d1f4ad3d8a	Fix build error introduced in bad merge of TLS stuff	7 years ago
Paul Banks	946e872f2f	Fix tests and listeners to work with Config changes (splitting host and port fields)	7 years ago
Paul Banks	e8c510332c	Support legacy watch.HandlerFunc type for backward compat reduces impact of change	7 years ago
Paul Banks	cd88b2a351	Basic `watch` support for connect proxy config and certificate endpoints. ... - Includes some bug fixes for previous `api` work and `agent` that weren't tested - Needed somewhat pervasive changes to support hash based blocking - some TODOs left in our watch toolchain that will explicitly fail on hash-based watches. - Integration into `connect` is partially done here but still WIP	7 years ago
Paul Banks	5310561c11	Refactor reloadableTLSConfig and verifyier shenanigans into simpler dynamicTLSConfig	7 years ago
Paul Banks	e00ca9a7b7	Connect verification and AuthZ	7 years ago
Paul Banks	10db79c8ae	Rework connect/proxy and command/connect/proxy. End to end demo working again	7 years ago
Paul Banks	26e65f6bfd	connect.Service based implementation after review feedback.	7 years ago