[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>
This commit is contained in:
27 files changed
+1422
-137
No files matched your search
@@ -0,0 +1,19 @@
|
||||
terraform {
|
||||
required_providers {
|
||||
enos = {
|
||||
source = "hashicorp.com/qti/enos"
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
variable "name" {
|
||||
description = "the binary name"
|
||||
}
|
||||
|
||||
resource "enos_local_exec" "find_binary" {
|
||||
inline = ["type -P ${var.name} || (echo \"\n\nCould not find ${var.name} executable. Have you installed it?\n\n\" && exit 1)"]
|
||||
}
|
||||
|
||||
output "path" {
|
||||
value = enos_local_exec.find_binary.stdout
|
||||
}
|
||||
Reference in new issue
Block a user