boundary

Commit Graph

Author	SHA1	Message	Date
Johan Brandhorst-Satzkorn	3c29308673	chore: Add license headers to all files	3 years ago
Michael Li	2f9727e8cf	chore(enos): Upload e2e test output (#2863 ) * chore(enos): Upload e2e go test output * chore(enos): Add retention period	3 years ago
Michael Li	5fd66b8d88	chore(enos): Remove unused skip_failing_bats_tests variable (#2844 )	3 years ago
Ryan Cragun	23f1cdea27	enos: make the local build target configurable (#2313 ) This makes the `make` build target that is used for local builder variant configurable. This will allow us to utilize the local builder variant in downstreams that might use different targets for their build. * Make the local build target configurable * Allow cross compiling `linux/amd64` on different platforms.	3 years ago
Michael Li	26a85ef61b	chore(e2e): Better output formatting (#2719 ) Updating the `go test` command to include a table summary of test results at the end. This is the same command used by unit tests.	3 years ago
Michael Li	1596b02e53	test(e2e): Add database migration test (#2627 ) * test(e2e): Add database migration test * chore(enos): Add enos scenario for migration test * chore(enos): Update go test command to use count option * doc(e2e): Update readme with migration test details * Fix: Typo * CR: Use different library * CR: Add additional context in comment * CR: Move some code from test into functions * doc(e2e): Add instructions to more easily retrieve environment variables * refact(e2e): Create some more methods to increase test readability	3 years ago
Michael Li	45171a3f56	refact(e2e): Changes to support an automated migration test (#2676 ) * refact(e2e): Move cleanup steps into each test The migration test needed to create some resources, but doesn't care about cleaning up because the test would take care of spinning down the docker container that it's using. To maintain flexibility going forward, we'll establish that tests are responsible for cleaning up (rather than the methods they use) * refact(e2e): Use new env var for skip check Currently, the e2e tests use the E2E_PASSWORD_AUTH_METHOD_ID environment variable to determine if the test should be skipped. However, the new migration test does not require a pre-existing boundary cluster and would not have this environment variable. As a result, we needed an alternative way to check if an e2e test should be skipped when running tests in ci. * refact(e2e): Create more common boundary methods * fix(e2e): Set to string value Co-authored-by: Johan Brandhorst-Satzkorn <johan.brandhorst@gmail.com>	3 years ago
Josh Brand	0857cbb663	fix(e2e): Add missing project tags for targets	3 years ago
Michael Li	719200612d	refact(e2e): Remove use of AwsHostSetCount env Instead of passing in the number of hosts created for a host set, we can just use the length of the IP addresses to determine that value.	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.	3 years ago
Michael Li	a12846d9af	refact(enos): Increase clarity in module variable name This variable defines the IP address of a target used in tests. We should pass in the address itself instead of a list of addresses that will get converted to a single address eventually anyways.	3 years ago
Michael Li	da0fb9d38a	test(e2e): Add dynamic host catalog test (AWS) This adds the initial set of tests that validate setting up a dynamic host catalog on AWS Co-authored-by: Josh Brand <jbrand@hashicorp.com>	4 years ago
Michael Li	8fe0d13caa	test(e2e): Add vault tests Adds the first set of vault tests. This test sets up vault as a credential store and creates a set of credentials for a target.	4 years ago
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
Jeff Mitchell	53b5e532d5	Remove deprecated methods/fields on targets (#2393 )	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

21 Commits (84b410974b73bfea8682f5fa63cc027ba145dfd4)