5 Commits (f9dfd024ed5f2ceb8959a295a43e070b9e1cbb6a)

Author	SHA1	Message	Date
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
Jaymala	611bf80279	Add infrastructure tags to Enos scenarios (#2486) ... Signed-off-by: Jaymala Sinha <jaymala@hashicorp.com> Signed-off-by: Jaymala Sinha <jaymala@hashicorp.com>	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
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
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