7 Commits (7bdbe8ab8eb6b7cc4577b75e9733c19c1fc69233)

Author	SHA1	Message	Date
Johan Brandhorst-Satzkorn	3c29308673	chore: Add license headers to all files	3 years ago
Michael Li	5365b29007	refact(e2e): Port enos smoke test into e2e test suite ... This adds a test case to the e2e test suite and unifies where testing is located.	4 years ago
Louis Ruch	b7684a857a	feat(ssh): Use HostId as HostKeyAlias for connect ssh helper (#2490)	4 years ago
Louis Ruch	42696d5da6	enos(smoke): Test brokered credential consumption instead of manually (#2456) ... passing private key to boundary connect	4 years ago
Josh Brand	8c0efb9715	Enos: add additional guards before authentication (#2382) ... * Enos: add additional guards before authentication Previously, we would see failures when the ALB in front of a cluster was alive and passing healthchecks, but the database behind had not been initialized yet. This adds a check with an unauth'd call to `auth-methods list` to validate the DB is up before auth.	4 years ago
Jeff Mitchell	d92cbac37d	Update enos/bats with changes	4 years ago
Ryan Cragun	9169c6bacb	[QTI-220] Add infrastructure integration testing (#2282) ... * [QTI-275] Add infrastructure integration testing On pull requests that originate from branches of the `hashicorp/boundary` repo, we now conditionally dispatch infrastructure integration tests using the Enos framework. The `integration` Enos scenario includes two `builder` variants which allow developers or CI to deploy a Boundary cluster in AWS using either a local `boundary` install bundle or that which is produced in the `build` workflow for CRT. The `test` variants determine which type of infrastructure integration test to run. At present those options are `cli_ui` (Bats CLI tests) or `smoke` (creates target instances and a target host catalog and verifies that `boundary` works). In addition to the new workflow and quality scenarios, we simplified the some `build` workflow steps and added Go module caching to speed up the build pipeline. See the [enos/README.md](https://github.com/hashicorp/boundary/blob/main/enos/README.md) for a detailed explanation on how to configure and execute Enos scenarios from your machine. Signed-off-by: Ryan Cragun <me@ryan.ec> Co-authored-by: Rebecca Willett <rwillett@hashicorp.com> Co-authored-by: Josh Branch <jbrand@hashicorp.com>	4 years ago