0 Fork 0

Files

T

Michael Li 843893c1c7 chore(e2e): Clean up enos variables (#6591 )

* chore(e2e): No more required enos variables

# Conflicts:
#	.github/workflows/enos-run.yml

* CR

2026-04-23 09:24:13 -04:00

.gitignore

test(hcp): Define TF module for long-lived resources (#5045 )

2024-09-05 12:08:07 -04:00

main.tf

chore(e2e): Remove aws_ssh_keypair requirement (#6583 )

2026-04-16 13:42:08 -04:00

outputs.tf

[COMPLIANCE] Update Copyright & License Headers

2026-04-06 15:48:57 +05:30

README.md

test(hcp): Define TF module for long-lived resources (#5045 )

2024-09-05 12:08:07 -04:00

variables.tf

chore(e2e): Clean up enos variables (#6591 )

2026-04-23 09:24:13 -04:00

README.md

Resources for HCP testing

This Terraform module defines resources needed to test against a long-lived HCP cluster.

Prerequisites

Gain access to the TFC hashicorp-qti org
Generate a TFC API token under Account Settings > Tokens

Usage

# Get AWS account credentials
doormat login
source <(doormat aws export --account ${AWS_ACCOUNT})

terraform login # enter TFC API token to the hashicorp-qti org
terraform init
terraform plan
terraform apply

The output contains information that we will need. For sensitive values, we will need to use these commands.

terraform state pull | jq .outputs.worker_tokens.value
terraform state pull | jq .outputs.bucket_secret_access_key.value

You can also find output information using the TFC UI by navigating to the boundary-hcp-resources workspace.

If any of these values have changed, we will need to update the Vault instance that stores these values.

Notes

Created a boundary-hcp-resources workspace in the TFC org
- Set Workflow to CLI-Driven
- Set Execution Mode to Local