9 Commits (e26ac3f388ffb217dff0c153d3ac123a501384ef)

Author	SHA1	Message	Date
hc-github-team-consul-core	c896ae06bf	Backport of Bring back parameter ServerExternalAddresses in GenerateToken endpoint into release/1.14.x (#15296) ... * backport of commit 4199a7c30a * backport of commit 53be93fb90 * backport of commit 1b0ce4e96c * backport of commit 1b4ee792cb * backport of commit 98f3d5aa51 * backport of commit 1f3b30b768 * Fix gomod for merging. Co-authored-by: Nitya Dhanushkodi <nitya@hashicorp.com> Co-authored-by: Derek Menteer <derek.menteer@hashicorp.com>	2 years ago
Nitya Dhanushkodi	5e156772f6	Remove ability to specify external addresses in GenerateToken endpoint (#14930) ... * Reverts "update generate token endpoint to take external addresses (#13844)" This reverts commit f47319b7c6.	2 years ago
cskh	eb26a7dee9	fix(cli): missing error message (#14959)	2 years ago
Chris S. Kim	b0a4c5c563	Include stream-related information in peering endpoints	2 years ago
freddygv	fac3ddc857	Use internal server certificate for peering TLS ... A previous commit introduced an internally-managed server certificate to use for peering-related purposes. Now the peering token has been updated to match that behavior: - The server name matches the structure of the server cert - The CA PEMs correspond to the Connect CA Note that if Conect is disabled, and by extension the Connect CA, we fall back to the previous behavior of returning the manually configured certs and local server SNI. Several tests were updated to use the gRPC TLS port since they enable Connect by default. This means that the peering token will embed the Connect CA, and the dialer will expect a TLS listener.	2 years ago
Eric Haberkorn	80e51ff907	Add exported services event to cluster peering replication. (#14797)	2 years ago
DanStough	2a2debee64	feat(peering): validate server name conflicts on establish	2 years ago
Chris S. Kim	7370f0a953	Fix test ordering (#14543)	2 years ago
DanStough	e617e7df3e	feat(cli): add initial peering cli commands	2 years ago