210 Commits (910d25efaa53c94e8dfe3df4e33fde4b5475c0b1)

Author	SHA1	Message	Date
Johan Brandhorst-Satzkorn	5dbcda512a	Fix enos bats test errors (#2468) ... * test(cli): Remove skips in CI for cli tests * fix(enos): Fix enos bats tests The tests still sometimes suffer from timing issues, but I was able to run a successful run (setup, run, destroy) of the tests from my machine at least once. There were 2 issues: - Some tests in groups.bats were hardcoding the default user id - The default grants for a user in a project were missing the permission to connect to a target. We now add this explicitly. Co-authored-by: Timothy Messier <tim.messier@gmail.com>	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
Michael Li	21e4b70e27	test(e2e): Add end-to-end tests (connect to first target) ... This adds the initial end-to-end tests. These tests validate the admin workflow of setting up their first target	4 years ago
Michael Li	172381f273	refact(enos): Move modules to its own file ... Enos allows module definitions to be in any file. This keeps all of the modules in one place (and also follows the model used by Vault)	4 years ago
Jeff Mitchell	53b5e532d5	Remove deprecated methods/fields on targets (#2393)	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
Jaymala	369f818f4c	Update Enos run (#2326) ... * Rotate the credential used for the Enos SSH Key * Use the enos provider from TFC Signed-off-by: Jaymala Sinha <jaymala@hashicorp.com>	4 years ago
Jeff Mitchell	9c03ef2105	Fix TF character usage	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