Ryan Cragun 27ab988205
[QT-695] Add config_mode variant to some scenarios (#26380)
Add `config_mode` variant to some scenarios so we can dynamically change
how we primarily configure the Vault cluster, either by a configuration
file or with environment variables.

As part of this change we also:
* Start consuming the Enos terraform provider from public Terraform
  registry.
* Remove the old `seal_ha_beta` variant as it is no longer required.
* Add a module that performs a `vault operator step-down` so that we can
  force leader elections in scenarios.
* Wire up an operator step-down into some scenarios to test both the old
  and new multiseal code paths during leader elections.

Signed-off-by: Ryan Cragun <me@ryan.ec>
2024-04-22 12:34:47 -06:00

54 lines
1.2 KiB
HCL

# Copyright (c) HashiCorp, Inc.
# SPDX-License-Identifier: BUSL-1.1
terraform {
required_providers {
enos = {
source = "registry.terraform.io/hashicorp-forge/enos"
}
}
}
variable "cluster_name" {
type = string
description = "The name of the cluster to load the image into"
}
variable "image" {
type = string
description = "The image name for the image to load, i.e. hashicorp/vault"
}
variable "tag" {
type = string
description = "The tag for the image to load, i.e. 1.12.0-dev"
}
variable "archive" {
type = string
description = "The path to the image archive to load"
default = null
}
resource "enos_local_kind_load_image" "vault" {
cluster_name = var.cluster_name
image = var.image
tag = var.tag
archive = var.archive
}
output "tag" {
value = var.tag
description = "The tag of the docker image to load without the tag, i.e. 1.10.0"
}
output "image" {
value = var.image
description = "The tag of the docker image to load without the tag, i.e. vault"
}
output "repository" {
value = enos_local_kind_load_image.vault.loaded_images.repository
description = "The name of the image's repository, i.e. hashicorp/vault"
}