mirror of
https://github.com/hashicorp/vault.git
synced 2025-09-19 21:01:09 +02:00
27ab988205
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>
28 lines
735 B
HCL
28 lines
735 B
HCL
# Copyright (c) HashiCorp, Inc.
|
|
# SPDX-License-Identifier: BUSL-1.1
|
|
|
|
# A shim seal module for shamir seals. For Shamir seals the enos_vault_init resource will take care
|
|
# of creating our seal.
|
|
|
|
terraform {
|
|
required_providers {
|
|
enos = {
|
|
source = "registry.terraform.io/hashicorp-forge/enos"
|
|
}
|
|
}
|
|
}
|
|
|
|
variable "cluster_id" { default = null }
|
|
variable "cluster_meta" { default = null }
|
|
variable "cluster_ssh_keypair" { default = null }
|
|
variable "common_tags" { default = null }
|
|
variable "image_id" { default = null }
|
|
variable "other_resources" {
|
|
type = list(string)
|
|
default = []
|
|
}
|
|
|
|
output "resource_name" { value = null }
|
|
output "resource_names" { value = var.other_resources }
|
|
output "attributes" { value = null }
|