aherman
/
boundary
mirror of https://github.com/hashicorp/boundary
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'dc93c63b95'
${ noResults }
boundary/enos/ci/hcp-resources
History
Tony dc93c63b95
Merge 576afa26c1 into af3848e797 		3 days ago
..
.gitignore test(hcp): Define TF module for long-lived resources (#5045) 1 year ago
README.md test(hcp): Define TF module for long-lived resources (#5045) 1 year ago
main.tf Merge 576afa26c1 into af3848e797 3 days ago
outputs.tf [COMPLIANCE] Update Copyright Headers (#6282) 3 weeks ago
variables.tf Merge 576afa26c1 into af3848e797 3 days ago

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