consul/test
Luke Kysow 70bb6a2abd
Run integration tests locally using amd64 (#14365)
Locally, always run integration tests using amd64, even if running
on an arm mac. This ensures the architecture locally always matches
the CI/CD environment.

In addition:
* Use consul:local for envoy integration and upgrade tests. Previously,
  consul:local was used for upgrade tests and consul-dev for integration
  tests. I didn't see a reason to use separate images as it's more
  confusing.
* By default, disable the requirement that aws credentials are set.
  These are only needed for the lambda tests and make it so you
  can't run any tests locally, even if you're not running the
  lambda tests. Now they'll only run if the LAMBDA_TESTS_ENABLED
  env var is set.
* Split out the building of the Docker image for integration
  tests into its own target from `dev-docker`. This allows us to always
  use an amd64 image without messing up the `dev-docker` target.
* Add support for passing GO_TEST_FLAGs to `test-envoy-integ` target.
* Add a wait_for_leader function because tests were failing locally
  without it.
2022-08-29 16:13:49 -07:00
..
bin
ca Update go version to 1.18.1 2022-04-18 11:41:10 -04:00
ca_path
client_certs
command/merge
hostname Update go version to 1.18.1 2022-04-18 11:41:10 -04:00
integration Run integration tests locally using amd64 (#14365) 2022-08-29 16:13:49 -07:00
key Update go version to 1.18.1 2022-04-18 11:41:10 -04:00
load Load test, upgrade packer version, fix k6s installation (#13382) 2022-06-15 09:29:38 -04:00
snapshot
CA-GENERATION.md
notes.txt