Files
nomad/e2e/terraform/main.tf
Tim Gross d6800c41c1 E2E: include Windows 2022 host in test targets (#26003)
Some time ago the Windows host we were using as a Nomad client agent test target
started failing to allow ssh connections. The underlying problem appears to be
with sysprep but I wasn't able to debug the exact cause as it's not an area I
have a lot of expertise in.

Swap out the deprecated Windows 2016 host for a Windows 2022 host. This will use
a base image provided by Amazon and then we'll use a userdata script to
bootstrap ssh and some target directories for Terraform to upload files to. The
more modern Windows will let us drop some of extra powershell scripts we were
using as well.

Fixes: https://hashicorp.atlassian.net/browse/NMD-151
Fixes: https://github.com/hashicorp/nomad-e2e/issues/125
2025-06-16 12:12:15 -04:00

24 lines
978 B
HCL

# Copyright (c) HashiCorp, Inc.
# SPDX-License-Identifier: BUSL-1.1
provider "aws" {
region = var.region
}
module "provision-infra" {
source = "./provision-infra"
server_count = var.server_count
client_count_linux = var.client_count_linux
client_count_windows_2022 = var.client_count_windows_2022
nomad_local_binary_server = var.nomad_local_binary_server
nomad_local_binary = var.nomad_local_binary
nomad_local_binary_client_ubuntu_jammy = var.nomad_local_binary_client_ubuntu_jammy
nomad_local_binary_client_windows_2022 = var.nomad_local_binary_client_windows_2022
nomad_license = var.nomad_license
consul_license = var.consul_license
nomad_region = var.nomad_region
instance_arch = var.instance_arch
name = var.name
}