3 Commits (d4e314cde86d3b439312e757c854b1752ccdecd9)

Author	SHA1	Message	Date
Elim Tsiagbey	1b1c8b3bf9	fix: Proxy closing listener with 0 connections left (#4389) ... * fix: Proxy closing listener with 0 connections left A bug was introduced in `0.15.0` where sessions with max connection counts were closed when the connections left hit 0. This issue was highlighted by a user: https://github.com/hashicorp/boundary/issues/4364. What was happening was when we have zero connections left the proxy code was closing the listener which closed its connections To fix this: - `boundary connect -target-id=xx -host-id=xx` command with no connections left will now wait for all connections to be closed and before exiting the session just like it did in `0.14.3` - As soon as there are no more connections left, the listener will close to stop accepting new connections - Fix issue where the websocket connection was throwing closing errors during the session teardown.	2 years ago
Jeff Mitchell	fff5f9506f	Migrate proxy logic to the API package (#4216) ... This allows arbitrary programs to have an easy mechanism to make connections through Boundary using Go. Internal cluster tests and test helpers have been migrated to use this package, as well as the `connect` command. --------- Co-authored-by: Johan Brandhorst-Satzkorn <johan.brandhorst@gmail.com>	2 years ago
Jeff Mitchell	fb4a5a98dc	Add some target fields and move some things around (#3879) ... In preparation for putting proxy code in the api package this creates some necessary fields in the target output and it pre-moves credential parsing and proxy handshake code to their new places. This will make the diff for the actual proxy code move quite a bit smaller. Co-authored-by: Johan Brandhorst-Satzkorn <johan.brandhorst@gmail.com>	2 years ago