mirror of
https://github.com/hashicorp/vault.git
synced 2026-06-13 10:56:26 -04:00
84935e4416
In order to take advantage of enos' ability to outline scenarios and to inventory what verification they perform we needed to retrofit all of that information to our existing scenarios and steps. This change introduces an initial set of descriptions and verification declarations that we can continue to refine over time. As doing this required that I re-read every scenanario in its entirety I also updated and fixed a few things along the way that I noticed, including adding a few small features to enos that we utilize to make handling initial versions programtic between versions instead of having a delta between our globals in each branch. * Update autopilot and in-place upgrade initial versions * Programatically determine which initial versions to use based on Vault version * Partially normalize steps between scenarios to make comparisons easier * Update the MOTD to explain that VAULT_ADDR and VAULT_TOKEN have been set * Add scenario and step descriptions to scenarios * Add initial scenario quality verification declarations to scenarios * Unpin Terraform in scenarios as >= 1.8.4 should work fine |
||
|---|---|---|
| .. | ||
| actionlint.yml | ||
| add-hashicorp-contributed-label.yml | ||
| backport-ce.yml | ||
| build-artifacts-ce.yml | ||
| build.yml | ||
| changelog-checker.yml | ||
| ci.yml | ||
| code-checker.yml | ||
| copywrite.yml | ||
| do-not-merge-checker.yml | ||
| enos-lint.yml | ||
| enos-release-testing-oss.yml | ||
| enos-run-k8s.yml | ||
| milestone-checker.yml | ||
| oss.yml | ||
| plugin-update-check.yml | ||
| plugin-update.yml | ||
| remove-labels.yml | ||
| security-scan.yml | ||
| stable-website.yaml | ||
| test-acc-dockeronly-nightly.yml | ||
| test-ci-bootstrap.yml | ||
| test-ci-cleanup.yml | ||
| test-enos-scenario-ui.yml | ||
| test-go.yml | ||
| test-run-acc-tests-for-path.yml | ||
| test-run-enos-scenario-matrix.yml | ||