68 Commits (84b410974b73bfea8682f5fa63cc027ba145dfd4)

Author	SHA1	Message	Date
Timothy Messier	45b15fab8c	ci: Start vault for cli ui tests	3 years ago
Josh Brand	9309154d05	Gate jobs to run only on OSS repo, adjust TIME_LIMIT for boundary (#2884)	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
Josh Brand	7d49a3a06b	Add automated cleanup for CI resources (#2814) ... * Add automated cleanup for CI resources	3 years ago
Michael Li	5fd66b8d88	chore(enos): Remove unused skip_failing_bats_tests variable (#2844)	3 years ago
Ashlee M Boyer	4b7f40c356	[check-legacy-links-format] Upgrading to latest workflow (#2832) ... * Upgrading to latest workflow * Updating docs-content-check-legacy-links-format hash * Undoing changes to workflow trigger	3 years ago
Ashlee M Boyer	e6be6431b2	docs: Migrate link formats (#2777) ... * Adding docs-content-check-legacy-links-format workflow * Adding test-link-rewrites workflow * Migrating links to new format	3 years ago
Irena Rindos	400f13a7e8	Revert "fix milestone check" (#2758) ... This reverts commit a283e8be5e.	3 years ago
Jeff Mitchell	9001642099	Use non-deprecated v3 checkout runner in milestone check (#2754) ... Move milestone-check.json to the right place	3 years ago
Irena Rindos	99cf985649	fix milestone check (#2753)	3 years ago
Jeff Mitchell	ee7bf3cde6	Add check to ensure milestone (#2747) ... * Add check to ensure milestone Stolen from https://github.com/hashicorp/vault/pull/18406 * Update .github/workflows/milestone-checker.yml Co-authored-by: Johan Brandhorst-Satzkorn <johan.brandhorst@gmail.com> * Pin grafana github actions ref Co-authored-by: Johan Brandhorst-Satzkorn <johan.brandhorst@gmail.com>	3 years ago
Michael Li	74f7ce93bc	chore(e2e): Update to use Vault 1.12.2 (#2726)	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
Mike Baum	cc42c51e5e	[QT-396] Ensure oss enos ci bootstrap workflow only runs in the oss repo (#2711)	3 years ago
Danielle	46037cf85a	Add Staticcheck to Build Pipeline (#2421) ... Run staticcheck linters on pull requests	3 years ago
Mike Baum	24c3d6824d	[QT-396] Add Enos CI bootstrapping scenarios (#2621) ... * Add Enos CI bootstrapping scenarios * Add GitHub Actions workflow for CI bootstrapping * Add service quotas limit increase request to Enos CI bootstrapping	3 years ago
emily neil	7cd5b5a320	Onboard boundary to use new version/VERSION file and reproducible actions-go-build (#2662) ... * Onboard boundary to use new .release/VERSION file and reproducible actions-go-build * Added automatic patch version bumps to end of release pipeline * Added back VersionMetadata to internal directory * Moved VERSION file to version/ * Update to current version * Using prepare workflow for pre-stable channel workflow * Test prepare workflow * PR feedback: allow builds to run builds locally without setting BIN_PATH * PR feedback: revert Enos changes * PR Feedback * Remove current branch from ci pipeline * Run make fmt	3 years ago
Michael Li	c20bd8a37e	chore(e2e): Update to use latest version of Vault CLI (#2585)	4 years ago
Michael Li	0424d379cf	refact(e2e): Reorganize test directory ... Rearranges the directory structure to align better with the enos scenarios. Tests will now be added in the `tests` directory, with a folder in the directory corresponding to an enos scenario.	4 years ago
Michael Anthony	b5ef8a516b	QT-351 - Output Terraform and provider version information in Enos workflows (#2564) ... * Add tf core and module version output step * Add generate step before getting versions	4 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
Michael Anthony	871cf0b963	chore: Add workflow for e2e tests ... This adds a github actions workflow to run the new e2e test suite Co-authored-by: Michael Anthony <manthony@hashicorp.com> Co-authored-by: Josh Brand <jbrand@hashicorp.com>	4 years ago
Timothy Messier	f28bcd4aa7	chore(cli): Run bats tests against boundary dev in CI ... Several of these tests are being skipped in the enos run. This seems to be due to differences in the setup that is performed. When these tests were run manually, `boundary dev` was used which performs some setup of resources automatically. However since enos uses a non-dev controller, a similar setup is performed via the enos modules. Until the discrepancies between the setup can be investigated, this adds a separate CI job to run the tests against `boundary dev`. These tests are all passing, without any being skipped. This test suite can still be useful even if the enos version is fixed, since this test suite will run much faster, and therefore identify failures sooner.	4 years ago
Ryan Cragun	6983bb7d41	enos: don't fail fast in enos integration matrix (#2416) ... Disable the fail-fast feature for the matrix strategy. This prevents a single failure to cascade to all jobs in the matrix. This prevents cases where other jobs fail before they're able to clean up resources. Signed-off-by: Ryan Cragun <me@ryan.ec>	4 years ago
Johan Brandhorst-Satzkorn	d4fce6fbe1	fix: Move enos job attribute into enos-run workflow (#2374) ... Maybe this will fix it? This doesn't make any sense.	4 years ago
Johan Brandhorst-Satzkorn	91e6857631	fix: Use correct yaml (#2373) ... Didn't notice this until it failed on main	4 years ago
Johan Brandhorst-Satzkorn	b6445adff0	feat: Stop enos jobs from failing CI pipelines (#2372) ... Enos jobs are still a bit unstable, we should use them as advisory for now. When they have gained more stability, we can let them fail pipelines again.	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
Michele Degges	047b9bea05	Merging ENT updates back into OSS (#2309)	4 years ago
Ryan Cragun	ed3014ead5	build: depend on the right output for metadata (#2306) ... Signed-off-by: Ryan Cragun <me@ryan.ec>	4 years ago
Ryan Cragun	ab3fe75537	build: generate the metadata file (#2302) ... Signed-off-by: Ryan Cragun <me@ryan.ec>	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
Michele Degges	63bfcaff61	[CI-only] Build updates (#2296)	4 years ago
Damian Debkowski	aa9bf6b6a5	chore(go) bump version to 1.18.4 (#2281)	4 years ago
Michele Degges	e7a32ebd68	[CI-Only] Support per-commit dev images and fossa scanning (#2255)	4 years ago
Sam Salisbury	cb9bdbe7e4	fix actions-docker-build invocation (#2223)	4 years ago
Johan Brandhorst-Satzkorn	e7273d65c2	Bump Go version to v1.18.3 (#2158) ... * chore: Bump Go version Go 1.18.3 has some security patches over 1.18.1. See https://go.dev/doc/devel/release#go1.18.minor * Fix formatting This was missed in a recent PR	4 years ago
Carlos Alcaide Corvo	ce0507ee99	Update UI artifacts consumption (#2074) ... Update UI artifacts consumption to allow UI editions	4 years ago
Jeff Mitchell	957fe19846	Bump to Go 1.18 (#2036)	4 years ago
Jeff Mitchell	0f961eb5f6	Bump Go to latest 1.17 (#2041)	4 years ago
Carlos Alcaide Corvo	960ed6a80f	Update from v2 to v3 all gh actions (#2030)	4 years ago
Carlos Alcaide Corvo	1342bd0183	Refactor build ci worfklow to decouple UI build (#1975) ... Refactor build workflow to stop building the UI and consuming UI artifacts	4 years ago
Timothy Messier	ec0f107ef5	fix(build): Run plugin script directly instead of with sh (#2025) ... These github actions run on Ubuntu based machine. Ubuntu by default links `/bin/sh` to dash. So by invoking the plugin.sh script as `/bin/sh ./plugins.sh` the script would run under `dash` despite the shebang line. A recent change that unified some of the build process, introduced additional bashisms into this script which is caused the build to fail. This updated the build system to just run the script directly, which will honor the shebang line. This seems like the best approach since the ubuntu machine has bash and the shebang line points to bash, so it is natural for developers to assume bashisms will work. See: f370abc1da https://github.com/actions/virtual-environments/blob/ubuntu20/20220410.2/images/linux/Ubuntu2004-Readme.md https://wiki.ubuntu.com/DashAsBinSh	4 years ago
Sarah Thompson	3d0b3d4072	Fix UI build caching and set network-timeout (#1875)	4 years ago
Michele Degges	9ec23fbf80	Remove setup-qemu step from Docker build job (#1873)	4 years ago
claire labry	1361261f67	[RDX-309] UI build timeout fix (#1870) ... * testing network concurrency flag * trigger ui build * trigger ui build * trigger ui build * whoops, cleaning up	4 years ago
modrake	2f7b4e5451	Docker version parity to reduce oss->ent merge conflicts (#1843)	4 years ago
Timothy Messier	8557442370	ci: Add plugin compile step (#1840) ... Some OS build steps were not compiling the plugins before compiling the boundary binary. This resulted in binaries that did not have plugins included, and would result in an error when starting a boundary server.	4 years ago
Michele Degges	84f6cc698c	Onboard Boundary to CRT (#1786) ... Onboard Boundary to Common Release Tooling Co-authored-by: mdrake <mdrake@hashicorp.com> Co-authored-by: jeanneryan <jeanneryan@hashicorp.com>	4 years ago