boundary

Commit Graph

Author	SHA1	Message	Date
Timothy Messier	d896f37493	Support reading multiple configuration files(#2504 ) feat(config): Support multiple files This updates the three subcommands that take a `-config` flag to to support multiple config files via a repeated `-config` flag. It updates the following subcommands: - `server` - `database init` - `database migrate` Note that the multiple file support only works if all config files are HCL, not JSON. Also note that the config files are concatenated together. There is no attempt to merge config files, so having the same stanza in multiple files can yield unexpected results, with only one of the stanzas being used. When used with these limitations understood, this provides a way to take different actions for different kinds of dynamic configuration changes. An example would be when using consul-template to render the configuration files for boundary. With the multi file support consul-template can render one config file for the controller stanza, and provide boundary with a dynamic database credential via vault. Then when the credential is rotated, consul-template can send boundary a SIGHUP to switch to the new credential without a restart. A separate template could be used to render a config for a stanza that does not support SIGHUP, such as the events stanza that gets its values via consul's KV. If these values change, consul-template can restart boundary so the new configuration is used. Co-authored-by: Timothy Messier <tim.messier@gmail.com> Co-authored-by: Jeff Mitchell <jeffrey.mitchell@gmail.com>	4 years ago
Timothy Messier	79866a287f	feat(schema): Add support for migration hooks This adds the ability to define hooks that will run prior to a schema migration. The hooks should only be used when a migration would fail due to data being in an invalid state, likely due to a bug in the previous schema definition. For example if a column was missing a constraint, and a new migration is attempting to add the constraint, there might already be values that violate the new constraint. In such cases, we would want the user to make a decision to address the data, and need to provide them with details about what data is problematic in case they want to manually address the problem. To help the user, if there is a sane way to address the data, we should provide an option to automatically "repair" the data, allowing the migration to continue. However, this still should be an explicit opt-in from the user, and we need to clearly describe what the repair option would do to the user so they understand the consequences of opting in. To accomplish this each migration can be provided a hook that contains a CheckFunc, RepairFunc, and RepairDescription. These functions must operate at the point-in-time of the migration immediately preceding the current migration, as as such they should not use and domain packages or repositories, instead they should use direct sql with the sql library. The description is used to explain what the RepairFunc will do. Hooks should be defined in `internal/db/schema/migrations/oss/oss.go` and registered with the schema edition. See the example in `internal/db/schema/manager_example_test.go` for more details.	4 years ago
Jeff Mitchell	9a4545e59e	Fix eventing and worker name setup (#2204 ) * Don't automatically create worker names, as this is now invalid for PKI workers * Fix a check in dev that clears out name/description in exactly the wrong cases * Change eventing setup to use a hostname-based ID instead of the name (which could change on every start anyways)	4 years ago
Johan Brandhorst-Satzkorn	ec608b79da	fix(cmd): Respect DB max open connections (#2094 ) Both the init and migrate commands were ignoring the configured max_open_connections database setting. This fix ensures that both commands respect the limits.	4 years ago
Jeff Mitchell	1be55b50c7	Pull up Server to top level of Init command (#1959 ) * Pull up Server to top level of Init command Init was using a local server variable but not passing in the existing command, resulting in the context being lost. This caused the command to fail to run since the changes to add logging to KMS plugins were introduced. This also fixes a couple of places that were not using the global const value for config KMS. * Fix test compilation	4 years ago
Jeff Mitchell	e596daf34d	Add hclog adapter and gating to eventer (#1915 ) This contains to related things: 1. An adapter allowing an hclog interface to take in information and send them to the eventer 2. A gate on the eventer, which is the analogue to the behavior prior to eventing where we'd ensure logs were not printed prior to the startup information. Without this, plugin logs using the hclog adapter will start showing up too early.	4 years ago
Jeff Mitchell	7eb29261b2	Update to go-kms-wrapping version 2, and plugin-based KMS (#1901 )	4 years ago
Jeff Mitchell	1c8e0ed1e1	Add scaffolding for external host plugins and convert aws/azure over (#1581 )	5 years ago
Jeff Mitchell	e9a8ede0d6	Move wrapper package back to SDK (#1511 ) TF uses this, so SDK is a decent place for it. It doesn't create dependencies between it and API.	5 years ago
Jeff Mitchell	081de3cf79	Migrate sdk/recovery to api/ and sdk/wrapper to internal (#1507 ) * `recovery` is only used by the API (and the main module, for decryption) * `wrapper` is only used by the CLI right now Moving these brings them closer to the code that uses them, and makes the SDK package a bit more clear in terms of functionality.	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	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
Todd Knight	5d17bd9eec	Error on `boundary database migrate` if the db hasn't been initialized (#1184 )	5 years ago
Jeff Mitchell	9649a19d23	Update CLI error codes to be consistent with `connect` (#976 )	5 years ago
Todd Knight	57d4bf2bfd	Removing dev migration feature and checks (#892 )	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

21 Commits (d66b92abe023e75f736b7e4df99bd7e4798b2d91)