CyberCoveLLC/threshold
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update Slack channel reference from #team-quality to #team-vault-automation (#6574)

Browse Source
This commit is contained in:
Luis (LT) Carbonell authored and GitHub committed 2026-04-08 10:01:23 -04:00
1 parent a420c93643
commit cda43e9708
1 file changed
+3 -3
Download Patch File Download Diff File Expand all files Collapse all files
enos/README.md
+3 -3
View File
@@ -147,7 +147,7 @@ Here are the steps to configure the GitHub Actions service user:
- Full access to the CI AWS account is required. - Full access to the CI AWS account is required.
**Notes:** **Notes:**
- For help with access to Terraform Cloud and the CI Account, contact the QT team on Slack (#team-quality) - For help with access to Terraform Cloud and the CI Account, contact the Vault Automation team on Slack (#team-vault-automation)
for an invite. After receiving an invite to Terraform Cloud, a personal access token can be created for an invite. After receiving an invite to Terraform Cloud, a personal access token can be created
by clicking `User Settings` --> `Tokens` --> `Create an API token`. by clicking `User Settings` --> `Tokens` --> `Create an API token`.
- Access to the AWS account can be done via Doormat, at: https://doormat.hashicorp.services/. - Access to the AWS account can be done via Doormat, at: https://doormat.hashicorp.services/.
@@ -157,7 +157,7 @@ Here are the steps to configure the GitHub Actions service user:
1. **Create the Terraform Cloud Workspace** - The name of the workspace to be created depends on the 1. **Create the Terraform Cloud Workspace** - The name of the workspace to be created depends on the
repository for which it is being created, but the pattern is: `<repository>-ci-service-user-iam`, repository for which it is being created, but the pattern is: `<repository>-ci-service-user-iam`,
e.g. `boundary-ci-service-user-iam`. It is important that the execution mode for the workspace be e.g. `boundary-ci-service-user-iam`. It is important that the execution mode for the workspace be
set to `local`. For help on setting up the workspace, contact the QT team on Slack (#team-quality) set to `local`. For help on setting up the workspace, contact the Vault Automation team on Slack (#team-vault-automation)
2. **Execute the Terraform module** 2. **Execute the Terraform module**
@@ -179,7 +179,7 @@ workspace must be created as follows:
1. **Create the Terraform Cloud Workspace** - The name workspace to be created depends on the repository 1. **Create the Terraform Cloud Workspace** - The name workspace to be created depends on the repository
for which it is being created, but the pattern is: `<repository>-ci-bootstrap`, e.g. for which it is being created, but the pattern is: `<repository>-ci-bootstrap`, e.g.
`boundary-ci-bootstrap`. It is important that the execution mode for the workspace be set to `boundary-ci-bootstrap`. It is important that the execution mode for the workspace be set to
`local`. For help on setting up the workspace, contact the QT team on Slack (#team-quality). `local`. For help on setting up the workspace, contact the Vault Automation team on Slack (#team-vault-automation).
Once the workspace has been created, changes to the bootstrap module will automatically be applied via Once the workspace has been created, changes to the bootstrap module will automatically be applied via
the GitHub PR workflow. Each time a PR is created for changes to files within that module the module the GitHub PR workflow. Each time a PR is created for changes to files within that module the module