34 Commits (ba85a3bc3fb2be769b3eaa4835eac93726c19bd1)

Author	SHA1	Message	Date
Chris Marchesi	947dc96b30	server: Add back controller shutdown on worker startup failure (#1432) ... * server: Add back controller shutdown on worker startup failure This adds back the controller shutdown call on worker failure. This was added in a15961e4 to address a panic discovered in testing, and was mistakenly thought to be unnecessary. This, however, covers multi-role scenarios where we have already started the controller, which needs to be shut down gracefully if possible if we can't start the worker. A nil check has been added to ensure the panic does not resurface. Co-authored-by: Jeff Mitchell <jeffrey.mitchell@gmail.com>	5 years ago
Jim	68dd2a66ba	Remove unneeded hclog dependencies as we move forward with events (#1433)	5 years ago
s-christoff	6b78108ecf	Update primary error functions to take a context, deprecate old functions (#1358) ... * add new error funcs which take a ctx and deprecate existing funcs * use context where available when writing error events * remove circular internal/errors pkg dep * suppress some chatty errors using errors.WithoutEvent() * convert auth oidc funcs to take context where needed to write events Co-authored-by: Jim <jlambert@hashicorp.com>	5 years ago
Chris Marchesi	a15961e461	Close connections on worker on shutdown, add force shutdown (#1354) ... This adds functionality to ensure that connections are closed on a worker when the server is shut down or reloaded. Connections are closed, and then the shutdown process waits for the next report to the controller to go through, waiting the grace period that was added in #1330. The rest of shutdown is then proceeded with. Listener shutdown has been moved to the start of the process to ensure that new connections can't be made while we are shutting down. Additionally, functionality has been added to force shut down servers after a second interrupt has been received after the first one. This takes the form of code in both the server and dev mode code paths that just performs an os.Exit if another shutdown is received during the normal shutdown process. Additionally, the commit also includes some refactoring to tests so that we could use some of the new E2E testing code to test session connections during shutdown and reload. Additionally, this fixes a panic in worker startup when there are no controllers defined. Looks like the shutdown call was attempting to call into the controller, not the worker. Finally, this also removes the extra shutdown within the outer worker startup. Shutdown is actually handled within the inner StartWorker(), attempting shutdown on errors was actually leading to potential use of an uninitialized worker, which is leading to panics in testing.	5 years ago
Jim	70ad081e39	Events: convert from hclog to events (#1409)	5 years ago
Jim	11124794bf	Events: add node for formatting/filtering cloudevents (#1390)	5 years ago
Jeff Mitchell	ed6c59a053	Update the rest of the shared libs locations	5 years ago
Jeff Mitchell	44329d4ff9	Repoint mlock import	5 years ago
Jeff Mitchell	9ba1948298	Remove telemetry calls as we aren't using them	5 years ago
Chris Marchesi	5a70875726	internal/servers/controller: Worker failure connection cleanup (#1340) ... This commit adds the support to do the following: * Mark connections for non-reporting workers as closed. This is the controller counterpart to the worker functionality (see #1330). This is written as a scheduled job that does the work DB-side in a single atomic query. * Works to reconcile states if such a broken controller-worker connection resumes and a worker reports a connection as connected that should be disconnected. In this case, the controller will send an update request, and the worker will honor it and terminate the connection. * Further refinement of the grace period setting has been added here. We have converged on the current server "liveness" setting as our default here, which is half of the previous 30s (15 seconds, in other words). Additionally, this is now configurable on the controller and worker side, with the caveat that it's currently impossible to do so in config as the setting has been untagged in HCL. This is exposed so that we can run some sophisticated testing scenarios where we skew the grace period to either the controller or worker to ensure the aforementioned reconciliation works. * Some repository functions have been added to support the new functionality, in addition to some test code to the worker to allow querying of session state while testing. * Finally, we've added some add timestamp subtraction functions as well, basically serving as the opposite of the addition functions.	5 years ago
Jeff Mitchell	2cbcf9a563	Update usage of shared-secure-libs (#1393)	5 years ago
Jim	1daa3ebefe	integrate events into the servers (#1355)	5 years ago
Jeff Mitchell	9c945b7021	Migrate ParseAddress to shared-secure-libs (#1313)	5 years ago
Jeff Mitchell	7ee8ddba6a	True up some spelling	5 years ago
Dylan Scott	4ae5003763	PR #1001: Postgres Connection Pooling Control (#1015)	5 years ago
Jeff Mitchell	9649a19d23	Update CLI error codes to be consistent with `connect` (#976)	5 years ago
Jeff Mitchell	4738ceee5d	Add TLS certificate and worker tag reloading on SIGHUP (ICU-1142) (ICU-1143) (#959)	5 years ago
Jeff Mitchell	e9da3a871d	Switch on CORS by default if not specified (#928)	5 years ago
Jeff Mitchell	d279a906ce	Allow public_cluster_addr to use an env var or file (#907) ... Co-authored-by: Jeff Malnick <malnick@gmail.com>	5 years ago
Jeff Mitchell	b61dd0ef36	Update schema version check text	5 years ago
Todd Knight	568594d1b3	Release the shared lock using a non cancelled context (#918)	5 years ago
Jeff Mitchell	61ec5b47e4	When running single-server mode, use public_cluster_addr if given (#904) ... When running single-server mode, use public_cluster_addr if given Right now you don't need to specify a controller address and we use the cluster listener address; this allows overriding it to the public_cluster_addr if one is given. If `controllers` is specified we allow it to be either the cluster listener or the public cluster address if one is specified before trying to parse and use it.	5 years ago
Jeff Mitchell	7cf74596bf	Update info output key name	5 years ago
Todd Knight	955ae41215	Support upgrading from old migration table name (#889)	5 years ago
Todd Knight	1f9fcad1cd	Adding Migrate Command (#872)	5 years ago
Jeff Mitchell	717a3b52ee	Add worker tagging (#862) ... This allows workers to have tags assigned to them, which can then be filtered to control which targets they are allowed to serve.	5 years ago
Todd Knight	ec6151d174	Organize DB Schema Migration Code and DB Init Checks (#842) ... Create Schema Manager and propagate contexts into the DB calls downstream. Add checks at controller startup and database init for correct schema version and schema migration dirty bit being set.	5 years ago
Michael Gaffney	94cb79bbdd	See how Boundary would look with gofumpt applied (#853) ... * See how Boundary would look with https://github.com/mvdan/gofumpt applied Results of running `gofumpt -w -s .` * Update tools file and Makefile for gofumpt Co-authored-by: Jeff Mitchell <jeffrey.mitchell@gmail.com>	5 years ago
Jeff Mitchell	6580d85388	Remove erronious IsGlobalUnicast check. (#845) ... Fixes the issue raised at https://www.boundaryproject.io/docs/configuration/worker#complete-configuration-example	5 years ago
Jeff Mitchell	e6c98f1454	Add logic to error on certain invalid listener configs (#838) ... This adds logic to error on certain invalid listener config: * If an address in the worker's "controller" set is unspecified or multicast or global unicast, error * If the controller's cluster address is unspecified, ensure public_cluster_addr is set This has been a source of some confusing behavior on some GitHub tickets and even on the team, so preventing it is probably a good idea. It also relaxes the restriction around controller address matching cluster address in single-server mode when using DNS names.	5 years ago
Jeff Mitchell	e2e4631929	Add ability to set public cluster address (#761)	6 years ago
Jeff Mitchell	10a41c914e	Force worker to use the local controller when running in combined mode (#429)	6 years ago
Jeff Mitchell	7fcbffbe88	Remove not-set value. (#427) ... I don't think the conditions exist here that necessitated it being introduced into Vault, but I do sometimes see a baffling condition where the address coming from the flag is empty. I don't think we need this so take it out.	6 years ago
Jeff Mitchell	38ce9d9eac	Combine controller and worker commands (#415)	6 years ago