content large_stringlengths 3 20.5k | url large_stringlengths 53 192 ⌀ | branch large_stringclasses 4
values | source large_stringclasses 51
values | embeddings listlengths 384 384 | score float64 -0.21 0.65 |
|---|---|---|---|---|---|
# Set up the GitHub Enterprise VCS provider These instructions are for using a self-hosted installation of GitHub Enterprise for HCP Terraform's VCS features. [GitHub.com has separate instructions](/terraform/cloud-docs/vcs/github), as do the [other supported VCS providers](/terraform/cloud-docs/vcs). Configuring a new... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/vcs/github-enterprise.mdx | main | terraform | [
0.008161977864801884,
-0.0075519573874771595,
0.006541186943650246,
-0.03977685794234276,
-0.012705644592642784,
0.004182594828307629,
-0.08559584617614746,
-0.030237972736358643,
0.03410409390926361,
0.04787847772240639,
-0.026068618521094322,
-0.05009499564766884,
0.00020401389338076115,
... | 0.048063 |
as follows: | Field name | Value | | -------------------------- | ----------------------------------------------------------------------------- | | Application Name | HCP Terraform (``) | | Homepage URL | `https://app.terraform.io` (or the URL of your Terraform Enterprise instance) | | Application Description | Any des... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/vcs/github-enterprise.mdx | main | terraform | [
0.011079467833042145,
0.04715749993920326,
-0.04888937994837761,
-0.06793779134750366,
-0.024102261289954185,
-0.006959100719541311,
-0.017468592151999474,
0.024425722658634186,
-0.04045649617910385,
0.04239747300744057,
-0.02450636588037014,
-0.09201160073280334,
0.06778456270694733,
-0.0... | 0.048729 |
will still use HTTPS. - Do not use your personal SSH key to connect HCP Terraform and GitHub Enterprise; generate a new one or use an existing key reserved for service access. - In the following steps, you must provide HCP Terraform with the private key. Although HCP Terraform does not display the text of the key to us... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/vcs/github-enterprise.mdx | main | terraform | [
0.022511430084705353,
0.017443086951971054,
-0.06309022009372711,
-0.0530291423201561,
-0.08259835839271545,
0.032440461218357086,
-0.03344159573316574,
-0.02652083709836006,
0.022646702826023102,
0.02357703074812889,
0.00530481431633234,
-0.03979767858982086,
0.06932025402784348,
-0.02751... | 0.029023 |
# Set up the Azure DevOps Services VCS provider using OAuth These instructions describe how to connect to `dev.azure.com` for VCS integration. Refer to the [VCS overview](/terraform/cloud-docs/vcs) for information about other systems. ## Overview Complete the following steps to connect to Azure DevOps Services VCS: 1. ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/vcs/azure-devops-services.mdx | main | terraform | [
0.002458862727507949,
-0.004567191004753113,
-0.04931549355387688,
-0.04461881145834923,
-0.03196089714765549,
-0.00310253887437284,
-0.03138740360736847,
-0.0015529070515185595,
0.046858999878168106,
0.09934917092323303,
-0.05713989958167076,
-0.09316971153020859,
0.03688395395874977,
-0.... | 0.043865 |
Click \*\*New client secret\*\* and complete the instructions when prompted to create a client secret. 1. Click \*\*Overview\*\* and leave this page open in a browser tab. In the next step, you will copy and paste the unique \*\*Application (client) ID\*\*, \*\*Directory (tenant) ID\*\* and \*\*Client Secret\*\* from t... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/vcs/azure-devops-services.mdx | main | terraform | [
-0.025787295773625374,
0.03143753483891487,
-0.02538924291729927,
-0.05823877826333046,
-0.0441567562520504,
0.029911605641245842,
0.013743618503212929,
-0.03636044263839722,
0.07093796879053116,
0.12399894744157791,
-0.007695906329900026,
-0.11177699267864227,
0.08369889110326767,
0.00308... | 0.043906 |
a `service\_terraform` file with the private key, and a `service\_terraform.pub` file with the public key: `ssh-keygen -t rsa -m PEM -f "/Users//.ssh/service\_terraform" -C "service\_terraform\_enterprise"` This SSH key \*\*must have an empty passphrase\*\*. HCP Terraform cannot use SSH keys that require a passphrase. ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/vcs/azure-devops-services.mdx | main | terraform | [
0.03877909108996391,
0.012333421967923641,
-0.044821906834840775,
-0.053862065076828,
-0.07263044267892838,
0.060335922986269,
-0.032472576946020126,
-0.04684099555015564,
0.018642699345946312,
0.100523941218853,
-0.026478689163923264,
-0.10677961260080338,
0.06771725416183472,
-0.01096372... | -0.001414 |
# Set up the GitHub.com OAuth VCS provider These instructions are for using GitHub.com for HCP Terraform's VCS features, using a per-organization OAuth connection with the permissions of one particular GitHub user. [GitHub Enterprise has separate instructions,](/terraform/enterprise/vcs/github-enterprise) as do the [ot... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/vcs/github.mdx | main | terraform | [
-0.009536766447126865,
-0.029541537165641785,
-0.024228587746620178,
-0.03408808633685112,
-0.03417156636714935,
-0.025683561339974403,
-0.05136888846755028,
-0.006074514705687761,
0.04665154591202736,
0.05202474445104599,
-0.04250768572092056,
-0.031966693699359894,
0.027049895375967026,
... | 0.027853 |
| Homepage URL | `https://app.terraform.io` (or the URL of your Terraform Enterprise instance) | | Application Description | Any description of your choice. | | Authorization callback URL | `https://app.terraform.io/` | ### Register the OAuth application 1. Click the "Register application" button, which creates the app... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/vcs/github.mdx | main | terraform | [
0.0005528905312530696,
0.06144542247056961,
0.004037976730614901,
-0.0584864467382431,
0.017946461215615273,
-0.004665589891374111,
-0.05211425572633743,
0.0012674586614593863,
-0.026700815185904503,
0.010539481416344643,
-0.028532102704048157,
-0.04417060315608978,
0.06385816633701324,
-0... | 0.041044 |
for service access. - In the following steps, you must provide HCP Terraform with the private key. Although HCP Terraform does not display the text of the key to users after it is entered, it retains it and will use it when authenticating to GitHub. - \*\*Protect this private key carefully.\*\* It can push code to the ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/vcs/github.mdx | main | terraform | [
0.019229868426918983,
0.0023422264494001865,
-0.0752880722284317,
-0.05658101662993431,
-0.07641003280878067,
0.02237630821764469,
-0.014070741832256317,
-0.01909523271024227,
0.027143605053424835,
0.06674683094024658,
-0.0074139670468866825,
-0.03489747643470764,
0.06174788251519203,
-0.0... | 0.021895 |
# Set up the GitLab EE and CE VCS provider These instructions are for using an on-premise installation of GitLab Enterprise Edition (EE) or GitLab Community Edition (CE) for HCP Terraform's VCS features. [GitLab.com has separate instructions,](/terraform/cloud-docs/vcs/gitlab-com) as do the [other supported VCS provide... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/vcs/gitlab-eece.mdx | main | terraform | [
-0.020168790593743324,
0.0210939422249794,
0.013323885388672352,
-0.043492771685123444,
-0.02884436585009098,
-0.03995158150792122,
-0.03723576292395592,
-0.04421831667423248,
0.03274795040488243,
0.02401736192405224,
-0.024192608892917633,
-0.06725640594959259,
0.0288777407258749,
-0.0121... | 0.011527 |
needs user access to repositories to create webhooks and ingress configurations. ~> \*\*Important\*\*: In GitLab CE or EE 10.6 and up, you may also need to enable \*\*Allow requests to the local network from hooks and services\*\* on the "Outbound requests" section inside the Admin area under Settings (`/admin/applicat... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/vcs/gitlab-eece.mdx | main | terraform | [
-0.07104860246181488,
0.03128761798143387,
-0.045734621584415436,
-0.02106134407222271,
-0.08170945197343826,
-0.12196633219718933,
0.001617639558389783,
-0.022346066311001778,
-0.0004246972384862602,
0.026776442304253578,
-0.021891571581363678,
-0.08581317216157913,
0.10265900939702988,
-... | 0.025671 |
the Scope of this VCS Provider: 1. Select the \*\*Selected Projects\*\* option and use the text field that appears to search for and select projects to enable. All current and future workspaces and Stacks for any selected projects can use repositories from this VCS Provider. 1. Click the \*\*Update VCS Provider\*\* but... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/vcs/gitlab-eece.mdx | main | terraform | [
-0.028948914259672165,
-0.01614544726908207,
0.0037325865123420954,
-0.03357285261154175,
-0.05486177280545235,
0.00611276226118207,
-0.015099101699888706,
-0.016951678320765495,
0.05057419836521149,
0.03511268272995949,
0.012532220222055912,
-0.07120638340711594,
0.10034944862127304,
-0.0... | -0.028242 |
# Connect to VCS Providers HCP Terraform is more powerful when you integrate it with your version control system (VCS) provider. Although you can use many of HCP Terraform's features without one, a VCS connection provides additional features and improved workflows. In particular: - When workspaces are linked to a VCS r... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/vcs/index.mdx | main | terraform | [
-0.036998458206653595,
-0.020165279507637024,
0.04084377735853195,
0.0008737402386032045,
-0.02899152785539627,
0.005972294136881828,
-0.08453336358070374,
-0.009200363419950008,
0.044726256281137466,
0.05705104395747185,
-0.021772537380456924,
-0.049750830978155136,
-0.005124696530401707,
... | 0.047886 |
than any given HCP Terraform user. Keep this in mind when selecting a VCS user, as it may affect your security posture in one or both systems. ### Webhooks HCP Terraform uses webhooks to monitor new commits and pull requests. - When someone adds new commits to a branch, any workspaces or Stack based on that branch will... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/vcs/index.mdx | main | terraform | [
-0.04232274368405342,
-0.0059141796082258224,
0.022767700254917145,
-0.022210197523236275,
-0.011575218290090561,
-0.017137454822659492,
-0.05276156961917877,
-0.04311148822307587,
0.057524796575307846,
0.09914550930261612,
-0.030263056978583336,
-0.03660633787512779,
0.011566594243049622,
... | 0.039512 |
you've used OAuth before, read the instructions carefully. Since HCP Terraform's security model treats each \_organization\_ as a separate OAuth application, we authenticate with OAuth's developer workflow, which is more complex than the standard user workflow. The exact steps to authenticate are different for each VCS... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/vcs/index.mdx | main | terraform | [
-0.011517966166138649,
0.02687847428023815,
0.020300807431340218,
-0.07746535539627075,
-0.050318051129579544,
-0.009326662868261337,
-0.012372860684990883,
-0.011119809001684189,
0.05821964889764786,
-0.007208936382085085,
-0.0403936430811882,
-0.08700558543205261,
0.06207452341914177,
-0... | -0.065045 |
# Set up the Azure DevOps Services VCS provider using personal access tokens These instructions describe how to use a personal access token to connect HCP Terraform to Azure DevOps Services VCS, which is hosted at `dev.azure.com`. Connecting to Azure DevOps Services VCS lets you take advantage of HCP Terraform's VCS fe... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/vcs/azure-devops-services-pat.mdx | main | terraform | [
-0.01330391876399517,
-0.018846450373530388,
0.000847235438413918,
-0.04055863618850708,
-0.04325256869196892,
0.037048134952783585,
0.005857859738171101,
-0.005766781512647867,
0.032610345631837845,
0.08373763412237167,
-0.07665081322193146,
-0.08891024440526962,
0.0388486310839653,
-0.00... | 0.043747 |
provider a name in the \*\*Name\*\* field. This field is optional. 1. In the second step under \*\*Set up provider\*\*, paste the Azure DevOps Services personal access token you copied in [step 2](#step-2-create-a-new-personal-access-token-in-azure-devops-services) into the \*\*Personal Access Token\*\* field. 1. Click... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/vcs/azure-devops-services-pat.mdx | main | terraform | [
-0.01858079619705677,
-0.012307207100093365,
-0.02055370807647705,
-0.007845068350434303,
-0.059427715837955475,
0.023056404665112495,
0.0405648797750473,
-0.055759258568286896,
0.036313191056251526,
0.11023612320423126,
-0.014370085671544075,
-0.1209777370095253,
0.06640653312206268,
0.00... | 0.067296 |
or Stacks based on your organization's repositories. | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/vcs/azure-devops-services-pat.mdx | main | terraform | [
-0.04794205352663994,
-0.12478195130825043,
-0.0809163749217987,
0.0013557045022025704,
-0.012576543726027012,
-0.06391367316246033,
-0.08544027805328369,
-0.0033300116192549467,
0.009230581112205982,
0.0035956106148660183,
0.053043875843286514,
0.06134037300944328,
-0.03621971979737282,
0... | 0.161867 |
# Set up the Bitbucket Cloud VCS provider This topic describes how to connect Bitbucket Cloud to HCP Terraform. Bitbucket Cloud is the cloud-hosted version of Bitbucket. For self-hosted Bitbucket Data Center instances, refer to [Configuring Bitbucket Data Center Access](/terraform/cloud-docs/vcs/bitbucket-data-center).... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/vcs/bitbucket-cloud.mdx | main | terraform | [
-0.026528485119342804,
0.005823589861392975,
-0.008289153687655926,
-0.0005930305342189968,
-0.008936723694205284,
-0.008327491581439972,
-0.061543434858322144,
-0.04205741360783577,
0.019822856411337852,
0.08841264992952347,
-0.031038548797369003,
-0.06587152928113937,
0.02811625972390175,
... | -0.047336 |
1. Click the "Save" button, which returns you to the OAuth settings page. 1. Find your new OAuth consumer under the "OAuth Consumers" heading, and click its name to reveal its details. Leave this page open in a browser tab. In the next step, you will copy and paste the unique \*\*Key\*\* and \*\*Secret.\*\* ## Step 3: ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/vcs/bitbucket-cloud.mdx | main | terraform | [
-0.044573742896318436,
0.03162364661693573,
-0.0034426364582031965,
-0.015548406168818474,
-0.0076164728961884975,
-0.01267895009368658,
-0.014774896204471588,
-0.006579377222806215,
0.0431811697781086,
0.05179489776492119,
-0.02675572596490383,
-0.08365849405527115,
0.09094978123903275,
-... | -0.089366 |
account you want HCP Terraform to act as, navigate to the SSH Keys settings page, add a new SSH key and paste the value of the SSH public key you just created. 1. In HCP Terraform's \*\*Add VCS Provider\*\* page, paste the text of the \*\*SSH private key\*\* you just created, and click the \*\*Add SSH Key\*\* button. #... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/vcs/bitbucket-cloud.mdx | main | terraform | [
0.01836523413658142,
-0.02031165361404419,
-0.014817573130130768,
-0.027323246002197266,
-0.07420496642589569,
0.04065720736980438,
-0.05296281725168228,
-0.03459201753139496,
-0.011851124465465546,
0.08402133733034134,
-0.002084401436150074,
-0.09512396901845932,
0.06418031454086304,
-0.0... | -0.017986 |
# Set up the Bitbucket Data Center VCS provider This topic describes how to connect Bitbucket Data Center to HCP Terraform. For instructions on how to connect Bitbucket Cloud, refer to [Configuring Bitbucket Cloud Access](/terraform/cloud-docs/vcs/bitbucket-cloud). Refer to [Connecting VCS Providers to HCP Terraform](/... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/vcs/bitbucket-data-center.mdx | main | terraform | [
-0.04416334256529808,
-0.027377702295780182,
0.014612273313105106,
-0.014386466704308987,
-0.04313958063721657,
0.020534111186861992,
-0.09034889191389084,
-0.033685386180877686,
-0.0033984528854489326,
0.08486950397491455,
-0.02568858303129673,
-0.04250270873308182,
0.027740569785237312,
... | -0.03351 |
described in [Create an application link](#create-an-application-link) or use keys from an existing application link: - To generate new keys, click \*\*Continue\*\*. Do not leave this screen until you have copied the key values. - To use existing keys, enable the \*\*Use Custom Keys\*\* option and enter them into the f... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/vcs/bitbucket-data-center.mdx | main | terraform | [
-0.07605278491973877,
-0.05565543472766876,
-0.08972332626581192,
-0.019887272268533707,
0.015821874141693115,
-0.025310441851615906,
0.0197703056037426,
0.06895279884338379,
0.048648666590452194,
0.08021952956914902,
0.023475537076592445,
-0.01145273819565773,
0.062271323055028915,
-0.051... | -0.038251 |
a dedicated service user account for this purpose. Because creating webhooks requires admin permissions, the account must have admin access to any shared repositories of Terraform configurations. Refer to [Requirements](#requirements) for more information. 1. Open the \*\*SSH keys\*\* page and click the profile icon. 1... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/vcs/bitbucket-data-center.mdx | main | terraform | [
-0.022127773612737656,
0.01802070438861847,
-0.07132475823163986,
-0.04610375687479973,
-0.07142633199691772,
-0.03481333702802658,
-0.03947959467768669,
-0.03000548481941223,
0.016590280458331108,
0.11019774526357651,
-0.020488543435931206,
-0.12093286216259003,
0.05336194485425949,
-0.02... | 0.031567 |
# Set up the Azure DevOps Server VCS provider These instructions describe how to connect to on-premise installations of Azure DevOps Server so that you can use HCP Terraform's VCS features. For instructions on how to set up Azure DevOps Services using OAuth, refer to [Set up the Azure DevOps Services VCS provider using... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/vcs/azure-devops-server.mdx | main | terraform | [
-0.017402980476617813,
0.006655454635620117,
-0.0013589723967015743,
-0.030002223327755928,
-0.020068490877747536,
0.011345542035996914,
-0.02894885651767254,
-0.03655419871211052,
0.042069707065820694,
0.0894387736916542,
-0.06670324504375458,
-0.048730138689279556,
0.0221718642860651,
0.... | 0.02608 |
Terraform 1. On the "Configure settings" step there is one textbox. Enter your Azure DevOps Server \*\*Personal Access Token\*\* from Step 2. Click the "Continue" button to continue to the next step. ## Step 4: Configure VCS Provider Scope on HCP Terraform (Optional) This step is optional. You can configure which works... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/vcs/azure-devops-server.mdx | main | terraform | [
-0.006802915595471859,
-0.03406898304820061,
-0.005383966490626335,
-0.005775206722319126,
-0.037894148379564285,
0.04337695240974426,
-0.012314185500144958,
-0.08092944324016571,
0.06472816318273544,
0.10601034760475159,
-0.04337337985634804,
-0.08078280836343765,
0.03511406481266022,
0.0... | 0.047004 |
# Troubleshoot VCS providers This page collects solutions to the most common problems our users encounter with VCS integration in HCP Terraform. ## Azure DevOps ### Required status checks not sending When configuring [status checks with Azure DevOps](https://learn.microsoft.com/en-us/azure/devops/repos/git/pr-status-po... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/vcs/troubleshooting.mdx | main | terraform | [
0.015184370800852776,
-0.0009333566413260996,
0.007036352995783091,
-0.023027872666716576,
-0.01904895529150963,
0.006625351961702108,
0.03987870737910271,
-0.15073595941066742,
0.031672801822423935,
0.07035091519355774,
-0.004180545918643475,
-0.1285148710012436,
0.05722746625542641,
-0.0... | 0.021601 |
the Bitbucket Web Post Hooks Plugin documentation describes how to manually enter a hook URL, HCP Terraform handles this automatically. Manually entered URLs can interfere with HCP Terraform's operation. To check the hook URLs for a repository, go to the repository's settings, then go to the "Hooks" page (in the "Workf... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/vcs/troubleshooting.mdx | main | terraform | [
-0.07239604741334915,
-0.04355493560433388,
-0.009006028063595295,
0.004178707953542471,
-0.055864471942186356,
-0.04656868427991867,
-0.05807671695947647,
-0.07640372961759567,
0.010230437852442265,
0.10406861454248428,
-0.01255726721137762,
-0.08750798553228378,
0.028607986867427826,
-0.... | -0.022601 |
errors This often happens when the VCS connection has been somehow broken: it might have had permissions revoked, been reconfigured, or had the repository removed. Check for these possibilities and contact HashiCorp support for further assistance, including any information you collected in your support ticket. ### `red... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/vcs/troubleshooting.mdx | main | terraform | [
-0.014173411764204502,
0.0073570371605455875,
0.0013297904515638947,
-0.06499762088060379,
-0.019707804545760155,
-0.08150045573711395,
-0.09781817346811295,
-0.05509471520781517,
0.057216204702854156,
0.03512614592909813,
-0.009703834541141987,
-0.05476390942931175,
0.028197528794407845,
... | -0.021827 |
errors, running additional diagnostics using the OpenSSL command may provide more information about the failure. First, attach a bash session to the application container: ``` docker exec -it ptfe\_atlas sh -c "stty rows 50 && stty cols 150 && bash" ``` Then run the `openssl s\_client` command, using the certificate at... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/vcs/troubleshooting.mdx | main | terraform | [
-0.02177046239376068,
0.08256052434444427,
-0.04074959084391594,
0.01445502694696188,
0.007419764529913664,
-0.10364940017461777,
-0.027274690568447113,
0.05330584943294525,
0.057550154626369476,
-0.024693526327610016,
-0.033586286008358,
-0.09746302664279938,
0.11959248781204224,
0.084459... | -0.050022 |
# Connect to Private VCS Providers Connect HCP Terraform to your private VCS provider using a self-hosted HCP Terraform agent to use HCP Terraform within your private network without exposing your provider to the public internet. @include "tfc-package-callouts/private-vcs.mdx" ## Background You can use HCP Terraform ag... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/vcs/private.mdx | main | terraform | [
0.013556471094489098,
-0.012115747667849064,
0.005650936160236597,
-0.048360321670770645,
-0.039777133613824844,
0.02992713637650013,
-0.048709578812122345,
-0.0015176606830209494,
0.01267161313444376,
0.016614748165011406,
-0.013790084980428219,
-0.09111737459897995,
0.03197247534990311,
... | 0.011969 |
in HCP Terraform (Organization \*\*Settings > Version Control > Events\*\*) - VCS events include errors that have resulted from making requests for private VCS during setup of the VCS Connection, and during normal operation. - This will not include messages during normal operations of private VCS. To aid in troubleshoo... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/vcs/private.mdx | main | terraform | [
0.07391348481178284,
0.01510699838399887,
0.06728807091712952,
-0.010440136305987835,
0.008839019574224949,
-0.007636417169123888,
-0.06178536266088486,
-0.07936703413724899,
0.03189403936266899,
0.06604129076004028,
0.006796856410801411,
-0.11424663662910461,
-0.0008516606176272035,
-0.00... | -0.024282 |
# Variables overview Variables let you customize configurations, modify Terraform's behavior, setup [dynamic provider credentials](/terraform/cloud-docs/dynamic-provider-credentials), and store information like static provider credentials. You can set variables specifically for each workspace or you can create variable... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/variables/index.mdx | main | terraform | [
-0.0023658417630940676,
-0.0016287489561364055,
0.005259988363832235,
0.02874952368438244,
-0.07475904375314713,
0.03074699267745018,
0.026213958859443665,
-0.04381122067570686,
-0.021743465214967728,
0.025435104966163635,
-0.029407812282443047,
-0.08443213999271393,
0.07707328349351883,
-... | -0.029758 |
| | ----------------------------- | ---------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/variables/index.mdx | main | terraform | [
-0.04067615047097206,
0.0016279533738270402,
-0.04379346966743469,
-0.03140496090054512,
-0.09659241884946823,
0.01186291128396988,
-0.0011829602299258113,
0.043840132653713226,
0.00023470541054848582,
-0.06208382919430733,
0.05728145316243172,
-0.02426823042333126,
-0.03413430601358414,
-... | 0.060961 |
and `.auto.tfvars` file variables that have the same key. ### 8. Workspace-specific variables Workspace-specific variables always overwrite variables from variable sets that have the same key. Refer to [overwrite variables from variable sets](/terraform/cloud-docs/variables/managing-variables#overwrite-variable-sets) f... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/variables/index.mdx | main | terraform | [
0.02488621138036251,
-0.006238655187189579,
0.04219992458820343,
0.008704892359673977,
-0.06642888486385345,
0.026730874553322792,
0.057821132242679596,
-0.08174169808626175,
0.008702477440237999,
0.026830971240997314,
-0.007325929589569569,
-0.02989085391163826,
0.05728716403245926,
0.004... | -0.037613 |
determining precedence. ### 13. Global variable sets Workspace and project-scoped variable sets always take precedence over global variable sets that are applied to all workspaces within an organization. Terraform does not allow global variable sets to contain variables with the same key, so they cannot conflict. ### 1... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/variables/index.mdx | main | terraform | [
0.008325055241584778,
0.004529065918177366,
0.031166765838861465,
-0.02619369886815548,
-0.040528297424316406,
0.00527715589851141,
0.024724489077925682,
-0.04975902661681175,
-0.014051919803023338,
0.04620249941945076,
0.010709686204791069,
-0.01742265373468399,
0.03750777617096901,
0.038... | -0.008821 |
\*\*Workspace-specific\*\* variable | | `h` | `1` | | Project-owned \*\*workspace-scoped\*\* variable set | | `y` | `2` | | Project-owned \*\*project-scoped\*\* variable set | | | `4` | | Organization-owned \*\*workspace-scoped\*\* variable set | | `z` | `3` | | Organization-owned \*\*project-scoped\*\* variable set | ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/variables/index.mdx | main | terraform | [
0.009154831059277058,
-0.007197486236691475,
-0.021884091198444366,
0.004550744313746691,
-0.06690710037946701,
-0.010778496973216534,
0.041472289711236954,
-0.057445477694272995,
-0.058064334094524384,
0.04563506320118904,
0.008128938265144825,
-0.12178585678339005,
0.07860127836465836,
-... | 0.03528 |
# Manage variables and variable sets You can set variables specifically for each workspace or you can create variable sets to reuse the same variables across multiple workspaces and Stacks. Refer to the [variables overview](/terraform/cloud-docs/variables) for more information about variable types, scope, and precedenc... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/variables/managing-variables.mdx | main | terraform | [
0.022401535883545876,
-0.027595745399594307,
-0.026399502530694008,
0.033591318875551224,
-0.06703879684209824,
-0.02538854256272316,
0.023636244237422943,
-0.05200415104627609,
-0.032263923436403275,
0.04150529205799103,
-0.0020583432633429766,
-0.08835375308990479,
0.056971002370119095,
... | 0.051829 |
and formatting. 1. Click \*\*Save variable\*\*. The variable now appears in the list of the workspace's variables and HCP Terraform will apply it to runs. ### Edit a variable To edit a variable on a workspace: 1. Click the ellipses next to the variable you want to edit and select \*\*Edit\*\*. 1. Make any desired chang... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/variables/managing-variables.mdx | main | terraform | [
0.017475003376603127,
0.0582665391266346,
0.022225892171263695,
0.04629766196012497,
-0.04650957137346268,
0.04136550799012184,
0.04863324016332626,
-0.09891514480113983,
0.007828562520444393,
0.07727818936109543,
-0.04603107273578644,
-0.06560316681861877,
0.0752442255616188,
-0.020488092... | -0.035832 |
Stacks, or workspaces:\*\* Use the text fields to search for and select workspaces, Stacks, and projects to apply this variable set to. This affects all current and future workspaces and Stacks for any selected projects. After creation, users can also [add this variable set to their workspaces](#apply-or-remove-variabl... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/variables/managing-variables.mdx | main | terraform | [
-0.024552449584007263,
0.011625736951828003,
0.020323533564805984,
0.0487469881772995,
-0.012727800756692886,
0.0007805271307006478,
0.04091034084558487,
-0.07104197889566422,
-0.014518375508487225,
0.04662133753299713,
-0.011581143364310265,
-0.09896790236234665,
0.06499101221561432,
-0.0... | 0.048588 |
In Stacks, you can use the [`store` block](/terraform/language/block/stack/tfdeploy/store) to access variable sets. Your Stack must be able to access the variable set you are targeting, by giving your Stack's project access, or by making the variable set globally available. You can then reference a variable set in your... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/variables/managing-variables.mdx | main | terraform | [
0.013791202567517757,
-0.015592947602272034,
-0.06023477762937546,
0.029918070882558823,
-0.12384483963251114,
0.01862887479364872,
0.01240831520408392,
-0.008990071713924408,
0.02130396105349064,
0.04724416881799698,
0.016323495656251907,
-0.11465933918952942,
0.05470814183354378,
-0.0448... | -0.051879 |
recommend passing credentials to Terraform as environment variables instead of Terraform variables when possible, since Terraform runs receive the full text of all Terraform variable values, including [sensitive](#sensitive-values) ones. It may print the values in logs and state files if the configuration sends the val... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/variables/managing-variables.mdx | main | terraform | [
-0.003573078429326415,
0.0063939886167645454,
-0.030024468898773193,
0.009112011641263962,
-0.09464119374752045,
0.030125373974442482,
0.030505986884236336,
-0.0012295427732169628,
-0.010343232192099094,
0.03852042555809021,
-0.05169463902711868,
-0.08519651740789413,
0.08595211058855057,
... | -0.052182 |
# HCP Terraform private registry overview HCP Terraform's private registry works similarly to the [public Terraform Registry](/terraform/registry) and helps you share [Terraform providers](/terraform/language/providers) and [Terraform modules](/terraform/language/modules) across your organization. It includes support f... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/registry/index.mdx | main | terraform | [
-0.016969328746199608,
-0.04199274629354477,
-0.020936068147420883,
-0.02157491259276867,
0.025375572964549065,
0.04227201268076897,
-0.028312234207987785,
-0.060091663151979446,
-0.009775454178452492,
0.023013433441519737,
0.006718916352838278,
-0.05912886932492256,
0.023772217333316803,
... | 0.07971 |
[vcs]: /terraform/cloud-docs/vcs # Publish private modules to the private registry This topic describes how to publish private modules to an organization's private registry. For instructions on adding modules from the public registry, refer to [Add modules from the Terraform registry](/terraform/cloud-docs/registry/add... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/registry/publish-modules.mdx | main | terraform | [
-0.033886250108480453,
-0.03382578864693642,
-0.04269443824887276,
0.027946704998612404,
0.02055446244776249,
0.019247058779001236,
-0.03296203911304474,
-0.029425015673041344,
0.039557069540023804,
0.06984959542751312,
0.04597879573702812,
-0.03625723719596863,
0.02562740631401539,
-0.012... | 0.036548 |
option in your organization settings. When disabled, you should store the source code for each module in separate repositories, otherwise HCP Terraform and Terraform Enterprise may publish new versions of all modules in the repository each time you create a new release tag. ## Publish a new module You can publish modul... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/registry/publish-modules.mdx | main | terraform | [
-0.00273302779532969,
-0.051420796662569046,
-0.03664948046207428,
0.02195633016526699,
0.005589573178440332,
0.026495305821299553,
-0.10969166457653046,
-0.06746458262205124,
0.027887117117643356,
0.09126319736242294,
0.01612616330385208,
-0.026637578383088112,
0.05390439182519913,
-0.040... | 0.001528 |
tags to identify module versions. Your repository must contain at least one release tag for you to publish a module. Release tag names must be a [semantic version](http://semver.org), which you can optionally prefix with a `v`. For example, `v1.0.4` and `0.9.2`. The registry ignores tags that do not match these formats... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/registry/publish-modules.mdx | main | terraform | [
0.01823953539133072,
-0.04553361237049103,
0.007699673064053059,
-0.0020425422117114067,
0.005968845449388027,
-0.003168324241414666,
-0.05901763588190079,
-0.04068687558174133,
-0.01361026056110859,
0.0509004145860672,
0.05598876252770424,
-0.06266318261623383,
0.039333514869213104,
-0.02... | -0.00635 |
for a single provider. This action is important if you have modules with the same name but with different providers. For example, if you have module repos named `terraform-aws-appserver` and `terraform-azure-appserver`, the registry treats them as alternate providers of the same `appserver` module. - \*\*Delete all pro... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/registry/publish-modules.mdx | main | terraform | [
-0.08107726275920868,
-0.04745561257004738,
-0.03603726625442505,
-0.012354173697531223,
0.0554787740111351,
-0.006302166730165482,
0.01862148940563202,
-0.10703309625387192,
0.06102649122476578,
0.04107687994837761,
0.07066133618354797,
0.01468600332736969,
0.0502191036939621,
0.008759058... | 0.01871 |
# Use the configuration designer HCP Terraform's private registry includes a configuration designer that can help you spend less time writing boilerplate code in a module-centric Terraform workflow. The configuration designer lets you outline a configuration for a new workspace by choosing any number of private modules... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/registry/design.mdx | main | terraform | [
-0.04051299765706062,
0.024049261584877968,
-0.021221531555056572,
0.013179420493543148,
0.005626922473311424,
-0.00761213107034564,
-0.05981694161891937,
-0.0389319472014904,
-0.041828300803899765,
0.08039737492799759,
-0.03994804620742798,
-0.06596031039953232,
0.07428555935621262,
-0.04... | 0.066503 |
HCP Terraform does not save output from previous configuration designer runs. | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/registry/design.mdx | main | terraform | [
0.04404082149267197,
0.055124878883361816,
0.016705114394426346,
0.007703529205173254,
0.009097657166421413,
0.02246668189764023,
-0.09167511761188507,
-0.09408906102180481,
-0.04142322018742561,
0.03636155277490616,
-0.030526177957654,
-0.07122088223695755,
0.06202815845608711,
-0.0680595... | -0.079019 |
# Publish private providers to the HCP Terraform private registry In addition to [curating public providers from the Terraform Registry](/terraform/cloud-docs/registry/add), you can publish private providers to an organization's HCP Terraform private registry. Once you have published a private provider through the API,... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/registry/publish-providers.mdx | main | terraform | [
-0.012579026632010937,
-0.011255146004259586,
-0.027422374114394188,
0.005256079137325287,
-0.025465218350291252,
0.017776433378458023,
-0.0272675808519125,
-0.05251257121562958,
-0.017714552581310272,
0.07499814033508301,
0.011839437298476696,
-0.05273284390568733,
0.04577906057238579,
0.... | 0.019267 |
and instead use [HashiCorp's public PGP key](https://www.hashicorp.com/.well-known/pgp-key.txt) in the the [create a version](#create-a-version) step. The key ID for HashiCorp's public ID is `34365D9472D7468F`, and you can verify the ID by [importing the public key locally](/terraform/tutorials/cli/verify-archive#downl... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/registry/publish-providers.mdx | main | terraform | [
-0.022690944373607635,
0.055337391793727875,
-0.045513786375522614,
-0.0255491454154253,
-0.015485920011997223,
-0.03339826688170433,
-0.06716971844434738,
-0.08327101916074753,
0.016627322882413864,
0.05221745744347572,
-0.004590052179992199,
-0.05339132621884346,
0.02672983519732952,
-0.... | -0.014175 |
instances of `ORG\_NAME` with the name of your organization. ```shell-session $ curl \ --header "Authorization: Bearer $TOKEN" \ --header "Content-Type: application/vnd.api+json" \ --request POST \ --data @platform.json \ https://app.terraform.io/api/v2/organizations/ORG\_NAME/registry-providers/private/ORG\_NAME/aws/v... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/registry/publish-providers.mdx | main | terraform | [
-0.04590954631567001,
0.014096505008637905,
-0.032182853668928146,
-0.029213305562734604,
0.0018046186305582523,
-0.0487714521586895,
-0.09262599796056747,
-0.011566569097340107,
0.03185390681028366,
0.12450224161148071,
-0.028777282685041428,
-0.04249155893921852,
0.028648963198065758,
-0... | 0.046045 |
[vcs]: /terraform/cloud-docs/vcs # Add public providers and modules to the HCP Terraform private registry You can add providers and modules from the public [Terraform Registry](/terraform/registry) to your HCP Terraform private registry. The private registry stores a pointer to these public providers and modules so tha... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/registry/add.mdx | main | terraform | [
-0.018309690058231354,
0.005596498027443886,
-0.03149046003818512,
-0.0047791143879294395,
0.023150471970438957,
0.04949188977479935,
-0.02667195536196232,
-0.026427891105413437,
-0.01371083501726389,
0.031324781477451324,
0.001563466154038906,
-0.07118190824985504,
-0.009487620554864407,
... | 0.064383 |
or Module Removing a public provider or module from a private registry does not remove it from the public Terraform Registry. Users in the organization can still use the removed provider or module without changing their configurations. To remove a public provider or module from an organization's private registry: 1. Si... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/registry/add.mdx | main | terraform | [
-0.04993986710906029,
0.037276994436979294,
-0.021153569221496582,
0.007252970244735479,
0.034158218652009964,
0.00036487754550762475,
-0.0019636680372059345,
-0.11177784204483032,
0.0030492807272821665,
0.018389498814940453,
0.05850328132510185,
0.007292882073670626,
0.011354375630617142,
... | 0.016625 |
# Publish Stack component configurations to the private registry Publish Stack component configurations to your organization's private registry to simplify sharing and versioning configurations with your teams. ## Background Stacks are made up of individual `component` blocks that each source a Terraform module. You de... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/registry/publish-stack-configuration.mdx | main | terraform | [
-0.015082729049026966,
-0.06963245570659637,
-0.028546391054987907,
0.0014442834071815014,
-0.032069120556116104,
0.004795308690518141,
-0.09068044275045395,
-0.0200788676738739,
0.024493012577295303,
0.025389011949300766,
-0.006737512070685625,
-0.07998604327440262,
0.022342480719089508,
... | 0.010877 |
all component configurations whenever you create a new tag in GitHub. ## Release new versions To release a new version of a component configuration, push a new release tag to the associated VCS repository. The HCP Terraform private registry automatically imports the configuration and creates a new version for that tag.... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/registry/publish-stack-configuration.mdx | main | terraform | [
0.012297048233449459,
-0.05170339718461037,
0.006307134870439768,
-0.013443699106574059,
0.026859089732170105,
0.0075398581102490425,
-0.0739239901304245,
-0.020953623577952385,
-0.0006676464108750224,
0.03076164238154888,
0.02272556722164154,
-0.0037384771276265383,
0.01344425231218338,
-... | 0.006682 |
# Use artifacts from the HCP Terraform private registry All users in an organization can view the private registry and use the available providers, Stack component configurations, and modules. A private registry has some key requirements and differences from the [public Terraform Registry](/terraform/registry): - \*\*L... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/registry/using.mdx | main | terraform | [
-0.03244415298104286,
-0.011042816564440727,
-0.04596254229545593,
-0.018519867211580276,
-0.012948795221745968,
-0.004786970093846321,
-0.02102692797780037,
-0.02845119871199131,
-0.010733612813055515,
0.040258608758449554,
0.025724465027451515,
-0.07970359921455383,
0.02938465029001236,
... | 0.058216 |
= "1.0.0" } ``` ### Use private providers and modules The syntax for referencing private providers in the [provider block](/terraform/language/providers/configuration#provider-configuration-1) `source` argument is `//`. For the SaaS version of HCP Terraform, the hostname is `app.terraform.io`. ```hcl terraform { requir... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/registry/using.mdx | main | terraform | [
-0.024988437071442604,
0.010577558539807796,
0.017182938754558563,
0.010705472901463509,
0.006625803653150797,
0.012142001651227474,
0.032507166266441345,
-0.026509946212172508,
0.006033366546034813,
0.0355960913002491,
-0.0058172824792563915,
-0.13010548055171967,
0.06597236543893814,
-0.... | 0.03229 |
more about defining providers in Stacks, refer to [Declare providers](/terraform/language/stacks/component/declare-providers). ### Modules Each `component` block specifies the Terraform module to use as the source for that component. To source a module from a Remote Git address, use the following syntax: `git:::///.git... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/registry/using.mdx | main | terraform | [
-0.061244916170835495,
-0.04271071031689644,
0.003792801173403859,
0.026536770164966583,
-0.022857598960399628,
-0.02948426641523838,
0.0011551621137186885,
0.0074408771470189095,
0.059907466173172,
0.05308639258146286,
0.01066647469997406,
-0.07094037532806396,
0.03675748407840729,
-0.007... | -0.024846 |
can also use private providers and modules from organizations that are sharing with the workspace's organization. ## Authentication configurations with private providers and modules To authenticate with HCP Terraform, you can use either a [user token](/terraform/cloud-docs/users-teams-organizations/users#api-tokens) or... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/registry/using.mdx | main | terraform | [
-0.0625804141163826,
-0.02378668449819088,
-0.03223135322332382,
-0.005725993774831295,
0.0155666284263134,
0.01650180295109749,
0.019448237493634224,
-0.06862718611955643,
0.031082307919859886,
0.014767623506486416,
-0.020119260996580124,
-0.0410357266664505,
0.04823587089776993,
0.035470... | 0.100486 |
# Test private modules in the HCP Terraform private registry You can configure HCP Terraform to automatically run tests for modules in your private registry. When enabled, HCP Terraform will run tests for every commit to the designated branch. This lets you verify that it is safe to publish new module versions. ## Enab... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/registry/test/index.mdx | main | terraform | [
0.010766732506453991,
-0.03723530098795891,
-0.011004078201949596,
0.023597920313477516,
0.0066809807904064655,
0.013015887700021267,
-0.12219604849815369,
-0.09338053315877914,
-0.038595087826251984,
0.06728512793779373,
0.02871575765311718,
-0.02725987695157528,
0.047108668833971024,
0.0... | -0.00106 |
to [Terraform test](/terraform/language/tests#providers). ## Generated module tests @include 'tfc-package-callouts/tests.mdx' HCP Terraform can generate [test files](/terraform/language/tests) for any private module in your registry. You can only generate tests one time per module. To generate tests for your module: 1.... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/registry/test/index.mdx | main | terraform | [
0.007530884351581335,
-0.004387464374303818,
-0.04487410932779312,
-0.007592170033603907,
-0.019693439826369286,
0.010411201976239681,
-0.05200766772031784,
-0.0846434235572815,
-0.014741675928235054,
0.04581297188997269,
0.0020365132950246334,
-0.07943540066480637,
0.0627361461520195,
-0.... | 0.003004 |
# Configure dynamic credentials for GCP in module testing @include 'tfc-package-callouts/registry-test-dynamic-credentials.mdx' You can use HCP Terraform's native OpenID Connect integration with Google Cloud Platform to get dynamic, short-lived credentials for module test runs. This approach uses GCP Workload Identity ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/registry/test/dynamic-credentials/gcp.mdx | main | terraform | [
-0.06107098609209061,
-0.008621668443083763,
-0.010781513527035713,
-0.04226310923695564,
-0.10198355466127396,
0.018929772078990936,
0.03379540145397186,
-0.016117867082357407,
-0.011405449360609055,
0.030520454049110413,
-0.03483681380748749,
-0.09658730030059814,
0.07405680418014526,
0.... | -0.042006 |
with your GCP project number. 5. Select the role \*\*Workload Identity User\*\* 6. Click \*\*Save\*\* Using the `gcloud` CLI: ```bash gcloud iam service-accounts add-iam-policy-binding terraform-module-test-sa@PROJECT\_ID.iam.gserviceaccount.com \ --role="roles/iam.workloadIdentityUser" \ --member="principalSet://iam.g... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/registry/test/dynamic-credentials/gcp.mdx | main | terraform | [
-0.035244911909103394,
0.015161870047450066,
0.03927493095397949,
-0.018751686438918114,
-0.05494975671172142,
-0.01766202598810196,
0.04622216895222664,
-0.07838121801614761,
0.01736299879848957,
0.09709391742944717,
-0.04215550795197487,
-0.11002448946237564,
0.06981997936964035,
0.00256... | -0.036172 |
`managed-by: terraform-test` to identify and manage test resources. You can then use IAM conditions to restrict the service account to only resources with those labels. ## Verify the configuration After configuring both GCP and HCP Terraform, verify the setup by running a test: 1. Navigate to your module in HCP Terrafo... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/registry/test/dynamic-credentials/gcp.mdx | main | terraform | [
-0.04595853388309479,
0.013237432576715946,
0.05916827172040939,
-0.01813133805990219,
-0.03040330857038498,
0.0130743607878685,
0.0857335701584816,
-0.08366558700799942,
0.010013259015977383,
0.04169365018606186,
-0.030883805826306343,
-0.10989148169755936,
0.09597048163414001,
0.01965732... | -0.006886 |
# Configure dynamic credentials for Vault in module testing @include 'tfc-package-callouts/registry-test-dynamic-credentials.mdx' You can use HCP Terraform's native OpenID Connect integration with HashiCorp Vault to get dynamic secrets for module test runs. This approach uses Vault's JWT/OIDC auth method to authenticat... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/registry/test/dynamic-credentials/vault.mdx | main | terraform | [
-0.009883180260658264,
0.046928562223911285,
-0.08475923538208008,
-0.03770115599036217,
-0.08385538309812546,
-0.002313723787665367,
-0.05376696214079857,
0.01722981594502926,
-0.005010959692299366,
-0.019676266238093376,
-0.015003436245024204,
-0.06952644139528275,
0.08048005402088165,
-... | -0.043605 |
resource "vault\_pki\_secret\_backend\_cert" "test\_cert" { backend = "pki" role = "module-tests" common\_name = "test.example.com" ttl = "24h" } # Use the certificate in your test resource "aws\_acm\_certificate" "test" { private\_key = vault\_pki\_secret\_backend\_cert.test\_cert.private\_key certificate\_body = vaul... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/registry/test/dynamic-credentials/vault.mdx | main | terraform | [
-0.03694881126284599,
0.0789816677570343,
-0.1132541224360466,
0.03622651472687721,
0.0009764450369402766,
-0.05238230526447296,
-0.030852416530251503,
-0.0018440784187987447,
0.04045729339122772,
-0.06915929168462753,
0.048784900456666946,
-0.08136794716119766,
0.13133381307125092,
0.0313... | -0.094346 |
vault audit enable file file\_path=/var/log/vault/audit.log ``` Then review the logs for entries with `type=response` and `auth.token\_type=batch`. ### Token claim debugging To see what claims HCP Terraform includes in module test tokens, use the manual token generation endpoint (requires organization owner permissions... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/registry/test/dynamic-credentials/vault.mdx | main | terraform | [
-0.003964457660913467,
0.05313313007354736,
0.0019494914449751377,
0.021354863420128822,
-0.015531397424638271,
-0.003924863878637552,
-0.0014685593778267503,
-0.039344724267721176,
0.022434089332818985,
0.04728633537888527,
-0.03747105598449707,
-0.07764572650194168,
0.06734547019004822,
... | -0.058852 |
# Configure dynamic credentials for AWS in module testing @include 'tfc-package-callouts/registry-test-dynamic-credentials.mdx' You can use HCP Terraform's native OpenID Connect integration with AWS to get dynamic, short-lived credentials for module test runs. This approach eliminates the need to store static AWS crede... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/registry/test/dynamic-credentials/aws.mdx | main | terraform | [
-0.04746690019965172,
0.01557544618844986,
-0.0545777902007103,
0.005868185311555862,
-0.07763126492500305,
0.027043672278523445,
-0.0102687431499362,
-0.0026316375005990267,
0.012294021435081959,
0.02770884521305561,
-0.03542856499552727,
-0.06683062762022018,
0.08563598990440369,
0.01068... | -0.017663 |
Click \*\*Tests\*\* in the module navigation 3. Click \*\*Configuration\*\* or \*\*Settings\*\* 4. In the \*\*Dynamic Credentials\*\* section, toggle \*\*Enable dynamic credentials\*\* 5. Select \*\*AWS\*\* as the provider 6. Enter the IAM role ARN, for example, `arn:aws:iam::123456789012:role/terraform-module-test-rol... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/registry/test/dynamic-credentials/aws.mdx | main | terraform | [
-0.015170524828135967,
-0.0037086333613842726,
-0.032983481884002686,
0.0538015216588974,
-0.042803261429071426,
-0.036722101271152496,
-0.006595579907298088,
-0.028933504596352577,
0.034885432571172714,
0.07115823030471802,
-0.04483859986066818,
-0.07762469351291656,
0.0740228071808815,
0... | -0.027669 |
"Action": [ "ec2:RunInstances", "ec2:TerminateInstances", "ec2:CreateTags", "ec2:Describe\*" ], "Resource": "\*", "Condition": { "StringEquals": { "aws:RequestedRegion": "us-east-1", "ec2:CreateAction": "RunInstances" } } }, { "Effect": "Allow", "Action": [ "ec2:TerminateInstances" ], "Resource": "arn:aws:ec2:us-east-1... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/registry/test/dynamic-credentials/aws.mdx | main | terraform | [
-0.006689391564577818,
0.0582067035138607,
-0.025055404752492905,
-0.01577475294470787,
0.016056250780820847,
-0.03917459025979042,
0.02971275895833969,
-0.06409298628568649,
-0.028465522453188896,
0.06232019513845444,
-0.010913094505667686,
-0.12705513834953308,
0.04831467196345329,
0.034... | 0.016692 |
# Use dynamic credentials with module testing @include 'tfc-package-callouts/registry-test-dynamic-credentials.mdx' Dynamic credentials in module testing let you use OpenID Connect (OIDC) to authenticate to your cloud provider during test runs. Instead of storing long-lived, static cloud credentials as environment vari... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/registry/test/dynamic-credentials/index.mdx | main | terraform | [
-0.06467247009277344,
0.02585449628531933,
-0.03610100969672203,
-0.025952747091650963,
-0.08164510875940323,
0.027550483122467995,
0.005560041405260563,
0.00016866058285813779,
0.030857820063829422,
-0.011882058344781399,
-0.03519327938556671,
-0.06581282615661621,
0.08471862971782684,
-0... | -0.020858 |
can use the HCP Terraform UI, the `/test-configuration` API endpoint, or environment variables in the test configuration to set the OIDC configuration for module tests directly on the module's test configuration. In the HCP Terraform UI: 1. Choose \*\*Registry\*\*, then click on your module. 1. Click \*\*Tests\*\*, the... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/registry/test/dynamic-credentials/index.mdx | main | terraform | [
-0.018442794680595398,
-0.00790943019092083,
-0.04214297980070114,
0.06610419601202011,
-0.040542375296354294,
-0.006289350334554911,
-0.05462890490889549,
-0.04490269348025322,
-0.02672484703361988,
-0.010151718743145466,
-0.006804994773119688,
-0.04486750438809395,
0.05454239249229431,
0... | -0.020172 |
Sentinel policies that validate OIDC configuration: ```sentinel import "tfrun" # Require OIDC for all test runs require\_oidc\_for\_tests = rule { tfrun.is\_test\_run implies tfrun.oidc\_enabled } # Enforce minimum token TTL minimum\_ttl = 300 # 5 minutes require\_minimum\_ttl = rule when tfrun.is\_test\_run and tfrun.... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/registry/test/dynamic-credentials/index.mdx | main | terraform | [
-0.07272212952375412,
0.007843174040317535,
-0.011715983971953392,
0.021995315328240395,
0.03320556506514549,
-0.10820814967155457,
0.022973116487264633,
0.007937959395349026,
-0.0035703787580132484,
0.03125385940074921,
0.004235835280269384,
-0.042476050555706024,
0.012330112047493458,
-0... | 0.126688 |
# Configure dynamic credentials for Azure in module testing @include 'tfc-package-callouts/registry-test-dynamic-credentials.mdx' You can use HCP Terraform's native OpenID Connect integration with Microsoft Azure to get dynamic, short-lived credentials for module test runs. This approach uses Azure AD federated identit... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/registry/test/dynamic-credentials/azure.mdx | main | terraform | [
-0.061918921768665314,
0.006569982040673494,
-0.09919431060552597,
0.018076706677675247,
-0.08340492844581604,
0.031102530658245087,
0.01878901943564415,
-0.024546882137656212,
-0.0013317642733454704,
0.07313314825296402,
-0.020940350368618965,
-0.07797117531299591,
0.07160009443759918,
0.... | -0.021762 |
your application name 8. Select your application and click \*\*Select\*\* 9. Click \*\*Review + assign\*\* Using the Azure CLI (for subscription-level access): ```bash az role assignment create \ --assignee \ --role "Contributor" \ --scope "/subscriptions/" ``` Replace `` with your service principal's object ID and `` ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/registry/test/dynamic-credentials/azure.mdx | main | terraform | [
-0.014217025600373745,
0.020800303667783737,
-0.0717749372124672,
-0.01820533350110054,
-0.07801293581724167,
0.08799323439598083,
0.08006151765584946,
-0.05642841011285782,
-0.022840019315481186,
0.11660971492528915,
-0.008179185912013054,
-0.13403929769992828,
0.12593939900398254,
0.0489... | -0.03126 |
"Storage Account Contributor" \ --scope "/subscriptions//resourceGroups/" ``` ### Custom roles for specific permissions For more granular control, create a custom role with only the required permissions: ```bash az role definition create --role-definition '{ "Name": "Module Test Role", "Description": "Custom role for m... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/registry/test/dynamic-credentials/azure.mdx | main | terraform | [
-0.008079762570559978,
0.01702313870191574,
-0.08032919466495514,
0.008744408376514912,
-0.04532423987984657,
0.03808791935443878,
0.12362663447856903,
-0.07949120551347733,
-0.03669165074825287,
0.09086430817842484,
0.00555220153182745,
-0.08403963595628738,
0.14462333917617798,
0.0868705... | -0.033769 |
and additional details ## Next steps - Learn about [dynamic credentials for module testing](/terraform/cloud-docs/registry/test/dynamic-credentials) - Configure dynamic credentials for other providers: - [AWS configuration](/terraform/cloud-docs/registry/test/dynamic-credentials/aws) - [GCP configuration](/terraform/cl... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/registry/test/dynamic-credentials/azure.mdx | main | terraform | [
-0.08126142621040344,
0.029310381039977074,
-0.021046679466962814,
0.02721649780869484,
-0.04027348384261131,
-0.040908973664045334,
0.0018529321532696486,
-0.009930919855833054,
0.02380194701254368,
0.0288467388600111,
-0.032915350049734116,
-0.030582956969738007,
0.05546042323112488,
0.0... | -0.024798 |
# Manage module versions You can manage the lifecycle of module versions in your organization’s private registry by deprecating or revoking module versions as you stop maintaining and supporting those versions. @include "tfc-package-callouts/manage-module-versions.mdx" Deprecating a module version adds warnings to the ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/registry/manage/module-versions.mdx | main | terraform | [
0.016200266778469086,
0.05007157474756241,
0.05099879205226898,
-0.027850758284330368,
0.04196850582957268,
-0.00019479783077258617,
-0.039609815925359726,
-0.07185486704111099,
0.013377057388424873,
0.03114054538309574,
0.011083021759986877,
0.010386263951659203,
0.013522496446967125,
-0.... | -0.011518 |
continue supporting. ### Deprecation warnings After you deprecate a module version, consumers of that version receive warnings in their operation outputs urging them to update that version in both HCP Terraform and the Terraform CLI. ~> \*\*Note\*\*: Only workspaces in the [remote or agent execution modes](/terraform/c... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/registry/manage/module-versions.mdx | main | terraform | [
-0.007648382801562548,
0.03159286454319954,
0.08275159448385239,
0.020202068611979485,
0.03202934190630913,
-0.006728473585098982,
-0.052724163979291916,
-0.07293190807104111,
-0.016399383544921875,
0.0388324074447155,
-0.0066978419199585915,
-0.05415366590023041,
0.05180772393941879,
-0.0... | -0.008579 |
used module version. Module version X.X.X of is revoked. ``` A run’s output mode affects where a version's revocation warnings appear. If a workspace is in the default [\*\*Structured Run Output\*\*](/terraform/cloud-docs/workspaces/settings#user-interface) mode, then module revocation warnings show up under a run’s \*... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/registry/manage/module-versions.mdx | main | terraform | [
-0.0215216763317585,
0.026216527447104454,
0.059626612812280655,
0.021549006924033165,
0.026735324412584305,
-0.04090069606900215,
-0.019980860874056816,
-0.0911598727107048,
0.06122562289237976,
0.018084600567817688,
0.0200334619730711,
0.04735797643661499,
0.03596486151218414,
-0.0044330... | 0.00059 |
# Manage artifact tags This topic describes how to add and manage tags for modules and providers hosted in your private registry. @include 'beta.mdx' ## Overview You can assign project tags to modules and providers in the registry, which helps you consistently use metadata across entities in your system. Use tags to in... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/registry/manage/tags.mdx | main | terraform | [
-0.01727842353284359,
0.011396719142794609,
-0.0004504246753640473,
-0.034317199140787125,
0.0020151366479694843,
-0.021676555275917053,
-0.018678339198231697,
-0.025522945448756218,
-0.003909940831363201,
0.058612655848264694,
-0.0413384772837162,
-0.10615959018468857,
0.06599593907594681,
... | 0.024196 |
# Encrypt your state and plan files The hold your own key (HYOK) feature lets you authenticate a key management system with HCP Terraform to encrypt HCP Terraform state and plan data with a key that you provide and control. ## Introduction @include 'tfc-package-callouts/hyok.mdx' Terraform artifacts can contain sensiti... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/hold-your-own-key/index.mdx | main | terraform | [
-0.0030395316425710917,
0.10530729591846466,
-0.02641674131155014,
-0.06076623871922493,
-0.03430244326591492,
0.012700608931481838,
0.014911575242877007,
-0.005871259141713381,
-0.015280642546713352,
0.006814951542764902,
-0.04428514093160629,
-0.05656418949365616,
0.07180973887443542,
-0... | 0.044449 |
for your HCP Terraform organization. An HYOK configuration in HCP Terraform configures the following: - How to authenticate to your KMS using OIDC. - Which key HCP Terraform uses for this configuration. - The name to identify of the configuration within HCP Terraform. After configuring a key, HCP Terraform will automat... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/hold-your-own-key/index.mdx | main | terraform | [
0.000376299925846979,
0.06680663675069809,
-0.01227858942002058,
0.003414517967030406,
-0.03402041643857956,
0.00009579845209373161,
-0.00016453170974273235,
-0.06648313254117966,
0.0215016957372427,
0.02222605235874653,
-0.033293962478637695,
-0.03791842982172966,
0.07604961842298508,
-0.... | 0.010356 |
# Hold your own key concepts The hold your own key (HYOK) feature lets you authenticate a key management system with HCP Terraform to encrypt HCP Terraform state and plan data with a key that you provide and control. @include 'tfc-package-callouts/hyok.mdx' Terraform artifacts can contain sensitive information, such as... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/hold-your-own-key/concepts.mdx | main | terraform | [
-0.030555682256817818,
0.09522267431020737,
-0.052130065858364105,
-0.03622562065720558,
-0.005800633225589991,
-0.05508573353290558,
0.025034219026565552,
-0.007348712999373674,
0.01406256016343832,
0.016878897324204445,
0.02452119253575802,
-0.028267795220017433,
0.058669205754995346,
-0... | 0.146161 |
HCP Terraform agent decrypts plan data before running your policies, ensuring your policies continue to run as expected. ## Encryption process HYOK uses a process called [envelope encryption](https://cloud.ibm.com/docs/key-protect?topic=key-protect-envelope-encryption#envelope-encryption-overview) to secure artifacts u... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/hold-your-own-key/concepts.mdx | main | terraform | [
-0.029179884120821953,
0.07259228080511093,
-0.010487344115972519,
-0.012638850137591362,
-0.01614348031580448,
-0.06942969560623169,
0.03193988651037216,
-0.05484049394726753,
0.051687877625226974,
0.04732512682676315,
-0.008618541993200779,
-0.04319734871387482,
0.05239207670092583,
-0.0... | 0.101647 |
the agent proxy detects the upload, which stream-encrypts the artifact with your workspace's DEK on its way to HCP Terraform's storage service. All HCP Terraform artifacts are encrypted using AES256-GCM, with AEAD based on the ID of the artifact to be encrypted: - Key size: 32 bytes - HKDF algo: `HMAC-SHA256` - Size of... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/hold-your-own-key/concepts.mdx | main | terraform | [
-0.015593179501593113,
0.08773704618215561,
0.02819051407277584,
-0.06528790295124054,
-0.008237199857831001,
-0.03864835947751999,
-0.0047441450878977776,
-0.07175861299037933,
0.0253065787255764,
0.04222040995955467,
-0.041456352919340134,
-0.05479547381401062,
0.04891561344265938,
-0.05... | 0.011276 |
necessary requests to your KMS. The HCP Terraform agent uses the KMS's encryption-as-a-service functionality to encrypt and decrypt the necessary data encryption key(s) without accessing the KEK. | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/hold-your-own-key/concepts.mdx | main | terraform | [
-0.020915117114782333,
0.08685299754142761,
0.004712685011327267,
-0.05860888585448265,
-0.004188058897852898,
0.004944830201566219,
0.00610645255073905,
-0.0858590379357338,
0.04333267733454704,
0.025337345898151398,
-0.013391315005719662,
-0.08654507249593735,
0.045653749257326126,
-0.08... | 0.096607 |
# Configure and manage keys Configure your key management system (KMS) and HCP Terraform to use the hold your own key (HYOK) feature to encrypt your sensitive Terraform artifacts. ## Background HCP Terraform lets you configure multiple HYOK configurations for an organization. Each HYOK configuration corresponds to a si... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/hold-your-own-key/configure.mdx | main | terraform | [
0.0034295981749892235,
0.05436639115214348,
-0.039177797734737396,
-0.031138379126787186,
-0.03758782148361206,
-0.04265345260500908,
0.01202654279768467,
-0.02412886917591095,
-0.0028691869229078293,
0.01737978868186474,
0.0010556173510849476,
-0.07309167087078094,
0.06672101467847824,
-0... | 0.055079 |
\*\*Audience\*\*: Leave this as the default value, `api://AzureADTokenExchange`. Make a note of the HYOK config name you choose here, you will use it later when you configure HCP Terraform. To use AWS with HYOK, you need to configure the following: - An OIDC Identity Provider for HCP Terraform. - An IAM role with a tru... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/hold-your-own-key/configure.mdx | main | terraform | [
-0.014526886865496635,
0.07323529571294785,
-0.04169277474284172,
0.022084522992372513,
-0.020065966993570328,
0.011936572380363941,
0.047826699912548065,
-0.03724642097949982,
-0.005953759886324406,
0.04661215841770172,
-0.011223536916077137,
-0.13013942539691925,
0.08534274250268936,
-0.... | 0.06682 |
encrypt and decrypt data using your key. For example, you could use the \*\*Cloud KMS CryptoKey Encrypter/Decrypter\*\* role, though you may want further scope access to only your key. ### Create a Workload Identity Pool and Provider Create a workload identity pool and provider by following the steps in [Configure Work... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/hold-your-own-key/configure.mdx | main | terraform | [
-0.020447785034775734,
0.08604907989501953,
-0.007294611074030399,
-0.02038138546049595,
-0.031948190182447433,
-0.02941046841442585,
0.061834052205085754,
-0.02425399050116539,
0.009343545883893967,
0.04834038391709328,
-0.013723318465054035,
-0.10455506294965744,
0.09160235524177551,
-0.... | 0.037248 |
is `unique-prod`: ```shell-session $ vault write -f transit/keys/unique-prod Key Value --- ----- allow\_plaintext\_backup false auto\_rotate\_period 0s deletion\_allowed false derived false exportable false imported\_key false keys map[1:1738617996] latest\_version 1 min\_available\_version 0 min\_decryption\_version 1... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/hold-your-own-key/configure.mdx | main | terraform | [
-0.015781573951244354,
0.02530091628432274,
-0.05468660965561867,
-0.05651988461613655,
-0.005008976440876722,
0.01998106762766838,
0.0523645393550396,
0.020702602341771126,
0.02154838852584362,
-0.03395470231771469,
-0.0024729345459491014,
-0.031710606068372726,
0.12422765046358109,
-0.06... | -0.081237 |
KMS to check for new key versions. The agent pool you specify is not used to perform Terraform runs. HCP Terraform continues to use the agent pool specified in your workspace's execution mode when performing runs. The agents running your workspace's operations do not require request forwarding, but you should update th... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/hold-your-own-key/configure.mdx | main | terraform | [
0.015002182684838772,
0.013607571832835674,
0.007390614133328199,
-0.005393143743276596,
-0.03882940858602524,
-0.0008438277873210609,
-0.011541982181370258,
-0.09863720834255219,
0.03330878168344498,
0.0720289796590805,
-0.029483972117304802,
-0.08155526965856552,
0.06803677976131439,
-0.... | 0.007345 |
for example `global` or `us-central1`. To configure your key in HCP Terraform, you need the \*\*Name\*\* of the key you created in the transit secrets engine. In the Vault configuration example above, this was `unique-prod`. ### Test the key configuration To test your HYOK configuration, click \*\*Test Connection\*\* o... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/hold-your-own-key/configure.mdx | main | terraform | [
0.009129680693149567,
0.04180740565061569,
-0.03498455137014389,
-0.02953210286796093,
-0.06119440123438835,
0.0005206175264902413,
-0.009099692106246948,
-0.03971288725733757,
-0.043587468564510345,
-0.0025444580242037773,
0.008011030033230782,
-0.08046593517065048,
0.09639906138181686,
-... | 0.018262 |
To revoke a key configuration: 1. Navigate to your organization's \*\*Settings\*\*. 1. Then to \*\*HYOK Encryption\*\*. 1. Click the \*\*Revoke\*\* button next to the HYOK configuration you want to revoke. When you revoke a key configuration, HCP Terraform migrates all of the workspaces that used that configuration to ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/hold-your-own-key/configure.mdx | main | terraform | [
0.007210952695459127,
0.11570805311203003,
0.04663270339369774,
-0.0079942736774683,
-0.02351437322795391,
-0.011167346499860287,
-0.006350861396640539,
-0.07259125262498856,
-0.0167658943682909,
0.005607604049146175,
0.0034025670029222965,
-0.009435002692043781,
0.08249952644109726,
-0.07... | -0.036365 |
[200]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/200 [201]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/201 [202]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/202 [204]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/204 [400]: https://developer.mozilla.org/en-US/docs/... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/api-docs/agents.mdx | main | terraform | [
-0.015784088522195816,
-0.01700746826827526,
-0.018668580800294876,
-0.028096551075577736,
-0.024631375446915627,
-0.08318780362606049,
-0.0621652752161026,
-0.07521579414606094,
-0.005580500699579716,
-0.03855427727103233,
0.03281282261013985,
0.0540321059525013,
0.006812138482928276,
-0.... | 0.052879 |
```shell curl \ --header "Authorization: Bearer $TOKEN" \ --header "Content-Type: application/vnd.api+json" \ --request GET \ https://app.terraform.io/api/v2/organizations/my-organization/agent-pools ``` ### Sample Response ```json { "data": [ { "id": "apool-yoGUFz5zcRMMz53i", "type": "agent-pools", "attributes": { "na... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/api-docs/agents.mdx | main | terraform | [
-0.04808203503489494,
0.0886593610048294,
0.007275454234331846,
-0.009627833031117916,
0.0009417864494025707,
-0.03998607024550438,
-0.029656842350959778,
-0.06834103167057037,
0.07679867744445801,
0.05454806238412857,
0.00907150562852621,
-0.10473334789276123,
0.013259796425700188,
0.0539... | 0.050225 |
### Sample Request ```shell curl \ --header "Authorization: Bearer $TOKEN" \ --header "Content-Type: application/vnd.api+json" \ --request GET \ https://app.terraform.io/api/v2/agent-pools/apool-MCf6kkxu5FyHbqhd ``` ### Sample Response ```json { "data": { "id": "apool-yoGUFz5zcRMMz53i", "type": "agent-pools", "attribut... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/api-docs/agents.mdx | main | terraform | [
-0.05781956762075424,
0.07838744670152664,
0.016050288453698158,
-0.003179118735715747,
0.010460895486176014,
-0.044277917593717575,
-0.03331691026687622,
-0.07066463679075241,
0.07489030808210373,
0.07580719888210297,
-0.0035940937232226133,
-0.10048182308673859,
0.012887515127658844,
0.0... | 0.034512 |
default value are required. | Key path | Type | Default | Description | |---------------------------------------------------|--------|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/api-docs/agents.mdx | main | terraform | [
0.06855788081884384,
-0.004717583768069744,
-0.04876028001308441,
-0.012768557295203209,
-0.09157141298055649,
0.022642426192760468,
0.009580298326909542,
0.04051562398672104,
0.02664242312312126,
-0.03390304744243622,
0.0388483889400959,
-0.06422821432352066,
-0.0005235570133663714,
-0.03... | 0.014966 |
"data": [] }, "allowed-workspaces": { "data": [ { "id": "ws-x9taqV23mxrGcDrn", "type": "workspaces" } ] }, "excluded-workspaces": "data": [ { "id": "ws-KyBgj8dDRvQqwBCC", "type": "workspaces" } ] }, "stacks": { "data": [] }, "allowed-stacks": { "data": [ { "id": "st-udYJjMCsnxU87uur", "type": "stacks" } ] }, "excluded-... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/api-docs/agents.mdx | main | terraform | [
-0.038871534168720245,
0.0948886051774025,
0.02756069228053093,
0.05787120386958122,
0.01926334761083126,
-0.06950200349092484,
-0.005836001131683588,
-0.06015042960643768,
0.05326489359140396,
-0.03674731031060219,
0.002337644575163722,
-0.004683312959969044,
0.017880462110042572,
0.01551... | -0.012084 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.