content large_stringlengths 3 20.5k | url large_stringlengths 54 193 | branch large_stringclasses 4
values | source large_stringclasses 42
values | embeddings listlengths 384 384 | score float64 -0.21 0.65 |
|---|---|---|---|---|---|
app v1alpha2 API groupntation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. [More information](https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources). | | `metadata` \_[ObjectMeta](https://kubernetes.io/d... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/integrations/kubernetes/api-reference.mdx | main | terraform | [
-0.013875964097678661,
0.03129616007208824,
0.03444284945726395,
0.006441288627684116,
-0.022966159507632256,
0.002552251797169447,
0.031713176518678665,
-0.05863584578037262,
0.10177240520715714,
0.05023123696446419,
-0.03068317100405693,
-0.07805639505386353,
0.010430239140987396,
-0.025... | 0.155777 |
the fields `ID` or `Name` is mandatory. More information: - [Remote state access controls](/terraform/cloud-docs/workspaces/state#remote-state-access-controls) \_Appears in:\_ - [RemoteStateSharing](#remotestatesharing) | Field | Description | | --- | --- | | `id` \_string\_ | Consumer Workspace ID. Must match pattern:... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/integrations/kubernetes/api-reference.mdx | main | terraform | [
-0.03523200750350952,
0.05547931417822838,
-0.003313687164336443,
0.02486656978726387,
-0.037361059337854385,
-0.01037246361374855,
0.03327029570937157,
-0.0959964320063591,
0.01832335814833641,
0.08308344334363937,
-0.024024220183491707,
-0.09578392654657364,
0.046882063150405884,
0.05207... | 0.038735 |
managed by the associated workspace. Once the destruction of these resources is successful, the operator deletes the workspace, and then deletes the custom resource. - `force`: Forcefully and immediately deletes the workspace and the custom resource. \_Appears in:\_ - [WorkspaceSpec](#workspacespec) #### Module Module ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/integrations/kubernetes/api-reference.mdx | main | terraform | [
-0.0867944061756134,
0.044343575835227966,
0.06165214255452156,
0.047784242779016495,
-0.0072157965041697025,
-0.07594874501228333,
0.019791854545474052,
-0.14008723199367523,
0.12348070740699768,
0.06338326632976532,
-0.04010576009750366,
0.01047575380653143,
0.04660353437066078,
0.005636... | 0.118924 |
how the operator should handle the deletion of resources when triggered by a user action or system event. There is one possible value: - `retain`: When the custom resource is deleted, the associated module is retained. `destroyOnDeletion` must be set to false. - `destroy`: Executes a destroy operation. Removes all reso... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/integrations/kubernetes/api-reference.mdx | main | terraform | [
-0.09191002696752548,
0.023670030757784843,
-0.033922601491212845,
0.07428011298179626,
0.008228981867432594,
-0.011114178225398064,
0.16972477734088898,
-0.05781418830156326,
0.0784253180027008,
-0.005247349385172129,
-0.002481257077306509,
0.007437840104103088,
0.03253859654068947,
0.053... | 0.140396 |
In CamelCase. [More information](https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds). | | `apiVersion` \_string\_ | APIVersion defines the versioned schema of this represePackage v1alpha2 contains API Schema definitions for the app v1alpha2 API groupPackage v1alpha2 contains... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/integrations/kubernetes/api-reference.mdx | main | terraform | [
0.009326728992164135,
0.013033025898039341,
0.022303618490695953,
-0.03636912256479263,
-0.0025694118812680244,
-0.041587501764297485,
-0.07152862846851349,
-0.015566227026283741,
0.03824453428387642,
0.001532538328319788,
0.01219861675053835,
-0.08847185969352722,
-0.014519920572638512,
-... | 0.123173 |
| --- | --- | | `id` \_string\_ | Current(both active and finished) HCP Terraform run ID. | | `configurationVersion` \_string\_ | The configuration version of this run. | | `outputRunID` \_string\_ | Run ID of the latest run that could update the outputs. | #### RunTrigger RunTrigger allows you to connect this workspac... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/integrations/kubernetes/api-reference.mdx | main | terraform | [
-0.04934672638773918,
0.009368348866701126,
0.013657934963703156,
0.006608520168811083,
-0.015855878591537476,
0.004828207194805145,
0.02124352566897869,
-0.10723717510700226,
0.016687491908669472,
0.06072878837585449,
-0.05125705897808075,
-0.08253074437379837,
0.056688569486141205,
-0.04... | 0.027795 |
Teams are groups of HCP Terraform users within an organization. If a user belongs to at least one team in an organization, they are considered a member of that organization. Only one of the fields `ID` or `Name` is allowed. At least one of the fields `ID` or `Name` is mandatory. More information: - [Teams overview](/te... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/integrations/kubernetes/api-reference.mdx | main | terraform | [
-0.018980564549565315,
0.05315258353948593,
-0.006982311140745878,
-0.02141638658940792,
-0.016856009140610695,
-0.029508618637919426,
0.027107689529657364,
-0.09676233679056168,
0.05631629750132561,
0.05160657688975334,
-0.048727668821811676,
-0.06896399706602097,
0.07392407953739166,
0.0... | 0.037572 |
| VersionID is a hash of the variable on the TFC end. | | `valueID` \_string\_ | ValueID is a hash of the variable on the CRD end. | | `category` \_string\_ | Category of the variable. | #### VersionControl VersionControl settings for the workspace's VCS repository, enabling the UI/VCS-driven run workflow. Omit this ar... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/integrations/kubernetes/api-reference.mdx | main | terraform | [
-0.034326523542404175,
0.06874502450227737,
0.004994137212634087,
-0.010639461688697338,
0.012691616080701351,
-0.023631544783711433,
-0.028872018679976463,
-0.04768501594662666,
0.11857288330793381,
0.031828559935092926,
-0.0237609650939703,
-0.08259368687868118,
-0.01756427064538002,
-0.... | 0.054847 |
of the fields `ID` or `Name` is mandatory. More information: - [Run tasks](/terraform/cloud-docs/workspaces/settings/run-tasks) \_Appears in:\_ - [WorkspaceSpec](#workspacespec) | Field | Description | | --- | --- | | `id` \_string\_ | Run Task ID. Must match pattern: `^task-[a-zA-Z0-9]+$` | | `name` \_string\_ | Run T... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/integrations/kubernetes/api-reference.mdx | main | terraform | [
-0.06179403141140938,
0.02429227903485298,
-0.0030903543811291456,
0.011883549392223358,
-0.005310471635311842,
-0.0431273952126503,
0.020899014547467232,
-0.05314101651310921,
0.01140047237277031,
0.08330200612545013,
-0.04692564532160759,
-0.11657434701919556,
0.05520707741379738,
0.0326... | 0.070704 |
that have the same type and the same key. More information: [Workspace variables](/terraform/cloud-docs/variables) and [Terraform variables](/terraform/cloud-docs/variables#terraform-variables). | | `remoteStateSharing` \_[RemoteStateSharing](#remotestatesharing)\_ | Remote state access between workspaces. By default, ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/integrations/kubernetes/api-reference.mdx | main | terraform | [
-0.039164893329143524,
-0.052382562309503555,
-0.016536770388484,
0.02759549766778946,
-0.043162573128938675,
0.025135941803455353,
0.011720892041921616,
-0.10978426039218903,
0.024151751771569252,
0.04727315530180931,
-0.01460384763777256,
-0.037269026041030884,
0.04179283604025841,
-0.02... | 0.048455 |
# HCP Terraform Operator for Kubernetes metrics This topic provides reference information about the Prometheus-compatible metrics available in the HCP Terraform and Terraform Enterprise operators for Kubernetes. ## Available metrics The operator exposes all metrics provided by the controller-runtime by default. Refer t... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/integrations/kubernetes/metrics.mdx | main | terraform | [
-0.01672447845339775,
-0.012267732061445713,
0.00482647679746151,
-0.024239685386419296,
-0.08071921765804291,
-0.009990667924284935,
0.0037546532694250345,
0.003097760723903775,
0.042356617748737335,
-0.002219011541455984,
-0.02533969283103943,
-0.1500280648469925,
0.0017737079178914428,
... | 0.159877 |
# Set up the HCP Terraform Operator for Kubernetes The HCP Terraform Operator for Kubernetes' CustomResourceDefinitions (CRD) allow you to dynamically create HCP Terraform workspaces with Terraform modules, populate workspace variables, and provision infrastructure with Terraform runs. You can install the operator with... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/integrations/kubernetes/setup.mdx | main | terraform | [
0.03664693981409073,
0.021942470222711563,
0.04096376523375511,
-0.04513119161128998,
-0.1095486506819725,
0.026013098657131195,
-0.027151240035891533,
-0.012567766942083836,
-0.0038080685772001743,
0.02907327376306057,
-0.07285365462303162,
-0.12483106553554535,
0.019748935475945473,
-0.0... | 0.102578 |
# HCP Terraform for AWS Service Catalog overview This integration allows administrators to curate a portfolio of pre-approved Terraform configurations on AWS Service Catalog. This enables end users like engineers, database administrators, and data scientists to deploy these Terraform configurations with a single action... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/integrations/aws-service-catalog/index.mdx | main | terraform | [
-0.009646443650126457,
0.014428242109715939,
-0.008471350185573101,
-0.0949026420712471,
-0.04654568433761597,
0.008271189406514168,
0.0033878509420901537,
-0.02461165189743042,
-0.034471917897462845,
0.01117449440062046,
-0.038146354258060455,
-0.11238360404968262,
0.04776490107178688,
-0... | 0.100836 |
# Workload identity Dynamic Provider Credentials are powered by Terraform Workload Identity, which allows HCP Terraform to present information about a Terraform workload to an external system – like its workspace, organization, or whether it’s a plan or apply – and allows other external systems to verify that the infor... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/dynamic-provider-credentials/workload-identity-tokens.mdx | main | terraform | [
-0.12173347175121307,
0.06933142989873886,
0.004221160896122456,
0.009393483400344849,
0.04599474370479584,
-0.036282945424318314,
0.07274419069290161,
-0.03981570899486542,
0.10573311150074005,
-0.04761670157313347,
-0.03435762971639633,
-0.02237970568239689,
0.06526867300271988,
-0.00124... | 0.177834 |
example: `organization:my-organization-name:project:Default Project:workspace:my-workspace-name:run\_phase:apply` | ### Custom Claims | Claim | Value | |--------------------------------------------------------|--------------------------------------------------------------------------------------------------------------... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/dynamic-provider-credentials/workload-identity-tokens.mdx | main | terraform | [
-0.12329836189746857,
0.0634426549077034,
-0.03302612900733948,
0.01878545619547367,
0.01786670833826065,
0.02828609012067318,
0.041862260550260544,
0.03745897486805916,
0.010490992106497288,
0.07366357743740082,
0.016254151239991188,
-0.10945501178503036,
0.04160410165786743,
-0.007519926... | 0.088455 |
# Dynamic provider credentials ~> \*\*Important:\*\* If you are self-hosting [HCP Terraform agents](/terraform/cloud-docs/agents), ensure your agents use [v1.7.0](/terraform/cloud-docs/agents/changelog#1-7-0-03-02-2023) or above. To use the latest dynamic credentials features, [upgrade your agents to the latest version... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/dynamic-provider-credentials/index.mdx | main | terraform | [
-0.0492151640355587,
-0.002654530107975006,
0.00826761033385992,
-0.013177512213587761,
-0.07404568046331406,
0.01290604006499052,
-0.011097967624664307,
-0.011161694303154945,
0.042996201664209366,
0.03079199232161045,
-0.04736968129873276,
-0.03797033056616783,
0.08810069411993027,
0.022... | -0.007951 |
variables for plan and apply operations, when providing dynamic credentials to run a query. The following variables are examples of run-specific environment variables you can use to configure dynamic provider credentials for queries: - [Amazon Web Services](/terraform/cloud-docs/dynamic-provider-credentials/aws-configu... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/dynamic-provider-credentials/index.mdx | main | terraform | [
-0.011093318462371826,
0.015654275193810463,
0.025975096970796585,
-0.010021486319601536,
-0.06849592179059982,
0.007131531368941069,
0.03255482390522957,
0.0003158358740620315,
0.02229858934879303,
0.058681316673755646,
-0.0484359972178936,
-0.10675270110368729,
0.03626660630106926,
-0.00... | -0.049115 |
# Use dynamic credentials with the Kubernetes and Helm providers ~> \*\*Important:\*\* If you are self-hosting [HCP Terraform agents](/terraform/cloud-docs/agents), ensure your agents use [v1.13.1](/terraform/cloud-docs/agents/changelog#1-13-1-10-25-2023) or above. To use the latest dynamic credentials features, [upgra... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/dynamic-provider-credentials/kubernetes-configuration.mdx | main | terraform | [
-0.01127429399639368,
0.013626912608742714,
0.011405296623706818,
-0.028584731742739677,
-0.0748453140258789,
0.05586477369070053,
-0.01961088925600052,
-0.007943772710859776,
0.06178657338023186,
0.028902532532811165,
-0.05772353708744049,
-0.09975028783082962,
0.08527559787034988,
-0.014... | 0.034218 |
"User" subjects, be aware that plan and apply phases are assigned different identities, each requiring specific bindings. Meaning you can tailor permissions for each Terraform operation. Planning operations usually require "read-only" permissions, while apply operations also require "write" access. !> \*\*Warning\*\*: ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/dynamic-provider-credentials/kubernetes-configuration.mdx | main | terraform | [
-0.015597444027662277,
0.0164646003395319,
0.04971443489193916,
-0.03261764347553253,
-0.08265197277069092,
0.008905396796762943,
0.017395740374922752,
-0.0075732688419520855,
0.017509646713733673,
0.02295827306807041,
-0.07426249235868454,
-0.1253804862499237,
0.057833779603242874,
0.0023... | 0.044929 |
} ``` The `tfc\_kubernetes\_dynamic\_credentials` variable is also available to use for single provider configurations, instead of the `KUBE\_TOKEN` environment variable. ```hcl provider "kubernetes" { host = var.cluster-endpoint-url cluster\_ca\_certificate = base64decode(var.cluster-endpoint-ca) token = file(var.tfc\... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/dynamic-provider-credentials/kubernetes-configuration.mdx | main | terraform | [
0.034979283809661865,
-0.00017034650954883546,
-0.018729669973254204,
-0.006515672896057367,
-0.08197104185819626,
0.04179270938038826,
0.019390638917684555,
0.06542782485485077,
0.07250785827636719,
-0.0018358987290412188,
-0.03868813440203667,
-0.11069846153259277,
0.01784701831638813,
0... | 0.037906 |
# Use dynamic credentials with the Vault provider ~> \*\*Important:\*\* If you are self-hosting [HCP Terraform agents](/terraform/cloud-docs/agents), ensure your agents use [v1.7.0](/terraform/cloud-docs/agents/changelog#1-7-0-03-02-2023) or above. To use the latest dynamic credentials features, [upgrade your agents to... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/dynamic-provider-credentials/vault-configuration.mdx | main | terraform | [
-0.003398524597287178,
0.027659377083182335,
-0.015465221367776394,
-0.03082803450524807,
-0.06950604915618896,
0.0233598779886961,
-0.0465150810778141,
0.007619073148816824,
0.03188526630401611,
0.010046477429568768,
-0.0427706241607666,
-0.07058175653219223,
0.1006648987531662,
-0.003065... | -0.056386 |
for a group of workspaces, or one role for all workspaces in an organization. You can also configure different roles for the plan and apply phases of a run. -> \*\*Note:\*\* If you set your `user\_claim` to be per workspace, then Vault ties the entity it creates to that workspace's name. If you rename the workspace tie... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/dynamic-provider-credentials/vault-configuration.mdx | main | terraform | [
-0.0122004933655262,
0.021251896396279335,
0.0308690145611763,
-0.01801442541182041,
-0.03095010668039322,
-0.02879183739423752,
-0.012192202731966972,
-0.045967843383550644,
0.045312073081731796,
-0.014186869375407696,
-0.024251023307442665,
-0.09130167216062546,
0.07796572893857956,
0.00... | -0.0404 |
later if self-managing agents. Optional if `TFC\_VAULT\_PLAN\_ROLE` and `TFC\_VAULT\_APPLY\_ROLE` are both provided. These variables are described [below](/terraform/cloud-docs/dynamic-provider-credentials/vault-configuration#optional-environment-variables) | ### Optional Environment Variables You may need to set these... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/dynamic-provider-credentials/vault-configuration.mdx | main | terraform | [
0.07114052772521973,
0.0710831955075264,
-0.017542637884616852,
-0.01470402255654335,
-0.03189465031027794,
0.0023994629736989737,
-0.01249787025153637,
-0.005980002228170633,
0.03125463426113129,
-0.0016730461502447724,
0.055904045701026917,
-0.1138748824596405,
0.04098604619503021,
0.028... | -0.078714 |
to the correct provider blocks. ```hcl variable "tfc\_vault\_dynamic\_credentials" { description = "Object containing Vault dynamic credentials configuration" type = object({ default = object({ token\_filename = string address = string namespace = string ca\_cert\_file = string }) aliases = map(object({ token\_filename... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/dynamic-provider-credentials/vault-configuration.mdx | main | terraform | [
0.013217534869909286,
0.06957259774208069,
0.007906957529485226,
-0.027024060487747192,
-0.059361010789871216,
-0.011393491178750992,
-0.01897462084889412,
0.019856106489896774,
0.019314933568239212,
-0.033353958278894424,
0.008815983310341835,
-0.12032198905944824,
0.05769118294119835,
0.... | -0.133217 |
# Dynamic Credentials with the HCP Provider ~> \*\*Important:\*\* If you are self-hosting [HCP Terraform agents](/terraform/cloud-docs/agents), ensure your agents use [v1.15.1](/terraform/cloud-docs/agents/changelog#1-15-1-05-01-2024) or above. To use the latest dynamic credentials features, [upgrade your agents to the... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/dynamic-provider-credentials/hcp-configuration.mdx | main | terraform | [
-0.04348991811275482,
0.023877833038568497,
0.012909901328384876,
-0.04109303280711174,
-0.07352220267057419,
0.05194440484046936,
-0.021968316286802292,
0.000528225558809936,
0.006495021749287844,
0.008067148737609386,
-0.042310211807489395,
-0.08243252336978912,
0.09121406823396683,
-0.0... | -0.032705 |
HCP. | | `TFC\_HCP\_RUN\_PROVIDER\_RESOURCE\_NAME` `TFC\_HCP\_RUN\_PROVIDER\_RESOURCE\_NAME[\_TAG]` `TFC\_DEFAULT\_HCP\_RUN\_PROVIDER\_RESOURCE\_NAME` | The resource name of the workload identity provider that will be used to assume the service principal | Requires \*\*v1.15.1\*\* or later if you use self-managing agen... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/dynamic-provider-credentials/hcp-configuration.mdx | main | terraform | [
-0.027372734621167183,
0.041677456349134445,
-0.07022037357091904,
-0.020219525322318077,
-0.07580447942018509,
0.06057308241724968,
0.07777706533670425,
0.07125192135572433,
-0.05264292284846306,
-0.023924367502331734,
0.06510547548532486,
-0.11416730284690857,
0.026128338649868965,
0.001... | 0.006987 |
# Specify multiple dynamic credential configurations ~> \*\*Important:\*\* If you are self-hosting [HCP Terraform agents](/terraform/cloud-docs/agents), ensure your agents use [v1.12.0](/terraform/cloud-docs/agents/changelog#1-12-0-07-26-2023) or above. To use the latest dynamic credentials features, [upgrade your agen... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/dynamic-provider-credentials/specifying-multiple-configurations.mdx | main | terraform | [
-0.02171122469007969,
-0.043039750307798386,
-0.006572933401912451,
-0.01348190475255251,
-0.07196318358182907,
0.001227623550221324,
0.03849094733595848,
-0.03293207660317421,
0.04908477142453194,
0.04398477077484131,
-0.07010599970817566,
-0.1266782283782959,
0.1123245358467102,
0.024747... | 0.001988 |
object({ default = object({ token\_filename = string address = string namespace = string ca\_cert\_file = string }) aliases = map(object({ token\_filename = string address = string namespace = string ca\_cert\_file = string })) }) } ``` Use the above object to map authentication information to the correct provider bloc... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/dynamic-provider-credentials/specifying-multiple-configurations.mdx | main | terraform | [
-0.0026504031848162413,
0.08519607782363892,
0.019689766690135002,
-0.008120662532746792,
-0.05001981183886528,
-0.0001201688646688126,
0.01389327272772789,
0.037784937769174576,
-0.011102941818535328,
-0.00996608380228281,
0.0063636223785579205,
-0.1329335868358612,
0.07090777903795242,
0... | -0.082754 |
# Manually generate workload identity tokens ~> \*\*Important:\*\* If you are self-hosting [HCP Terraform agents](/terraform/cloud-docs/agents), ensure your agents use [v1.7.0](/terraform/cloud-docs/agents/changelog#1-7-0-03-02-2023) or above. To use the latest dynamic credentials features, [upgrade your agents to the ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/dynamic-provider-credentials/manual-generation.mdx | main | terraform | [
-0.056035153567790985,
0.007772567216306925,
0.013738926500082016,
-0.010942584834992886,
-0.04388663172721863,
-0.009971238672733307,
0.018919887021183968,
-0.02159169875085354,
0.03549806773662567,
0.04272804036736488,
-0.07428254187107086,
-0.10665173828601837,
0.06280957907438278,
0.02... | 0.056111 |
# Use dynamic credentials with the AWS provider You can use HCP Terraform’s native OpenID Connect integration with AWS to get [dynamic credentials](/terraform/cloud-docs/dynamic-provider-credentials) for the AWS provider in your HCP Terraform runs. Configuring the integration requires the following steps: 1. \*\*[Confi... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/dynamic-provider-credentials/aws-configuration.mdx | main | terraform | [
-0.02589697204530239,
0.013182044960558414,
-0.006335445214062929,
-0.015660006552934647,
-0.09390746802091599,
0.045056648552417755,
-0.004069145768880844,
-0.0007432337151840329,
0.0061073899269104,
0.02619166113436222,
-0.07087574154138565,
-0.11583250015974045,
0.10274636000394821,
-0.... | -0.02889 |
"organization:ORG\_NAME:project:PROJECT\_NAME:workspace:WORKSPACE\_NAME:run\_phase:\*" } } } ``` !> \*\*Warning\*\*: you should always check, at minimum, the audience and the name of the organization in order to prevent unauthorized access from other HCP Terraform organizations! A permissions policy needs to be added t... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/dynamic-provider-credentials/aws-configuration.mdx | main | terraform | [
-0.03466051071882248,
0.03306035324931145,
-0.018079061061143875,
-0.024117128923535347,
0.03622899204492569,
-0.01001038122922182,
0.006526393815875053,
-0.07412576675415039,
0.02800830826163292,
0.052042145282030106,
-0.0051819696091115475,
-0.08409614115953445,
0.07500229775905609,
-0.0... | 0.018718 |
by configuring the variables prefixed with `TFC\_DEFAULT\_`. For more details, see [Specifying Multiple Configurations](/terraform/cloud-docs/dynamic-provider-credentials/specifying-multiple-configurations). #### Required Terraform Variable To use additional configurations, add the following code to your Terraform conf... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/dynamic-provider-credentials/aws-configuration.mdx | main | terraform | [
-0.0007910667918622494,
0.059265464544296265,
-0.0163221824914217,
-0.021185750141739845,
-0.09817098826169968,
0.056694746017456055,
0.031944390386343,
0.03868484124541283,
-0.023511474952101707,
0.016610583290457726,
-0.030933726578950882,
-0.13117513060569763,
0.10346376150846481,
0.012... | -0.087926 |
# Use dynamic credentials with the Azure provider You can use HCP Terraform’s native OpenID Connect integration with Azure to get [dynamic credentials](/terraform/cloud-docs/dynamic-provider-credentials) for the AzureRM or Microsoft Entra ID providers in your HCP Terraform runs. Configuring the integration requires the... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/dynamic-provider-credentials/azure-configuration.mdx | main | terraform | [
-0.02148880995810032,
0.011179711669683456,
-0.009831665083765984,
-0.00178519228938967,
-0.08434005081653595,
0.0636492520570755,
0.016245270147919655,
-0.02639000117778778,
0.002775004366412759,
0.04739051312208176,
-0.0631384402513504,
-0.10630788654088974,
0.1133195161819458,
0.0253241... | -0.02493 |
be created for each workspace using dynamic credentials: one that matches `run\_phase:plan` and one that matches `run\_phase:apply`. ## Configure HCP Terraform If you are configuring a Stack, refer to [Authenticate a Stack](/terraform/language/stacks/deploy/authenticate) to learn how to use the `identity\_token` block ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/dynamic-provider-credentials/azure-configuration.mdx | main | terraform | [
-0.039049357175827026,
-0.016385884955525398,
0.01691761240363121,
0.0012699250364676118,
-0.1041463166475296,
0.03707553446292877,
0.02742038480937481,
-0.026479361578822136,
0.013350892812013626,
0.052717044949531555,
-0.056920718401670456,
-0.12100475281476974,
0.09328806400299072,
0.01... | -0.050541 |
details to the correct provider blocks. ```hcl variable "tfc\_azure\_dynamic\_credentials" { description = "Object containing Azure dynamic credentials configuration" type = object({ default = object({ client\_id\_file\_path = string oidc\_token\_file\_path = string }) aliases = map(object({ client\_id\_file\_path = st... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/dynamic-provider-credentials/azure-configuration.mdx | main | terraform | [
-0.02232283726334572,
0.053835395723581314,
-0.002721520373597741,
0.005810159724205732,
-0.08022374659776688,
0.06743766367435455,
0.0863378569483757,
0.05803107097744942,
0.003985730465501547,
0.03918557986617088,
-0.011492731049656868,
-0.12232058495283127,
0.1270386129617691,
0.0689660... | -0.087947 |
# Use dynamic credentials with the GCP provider ~> \*\*Important:\*\* If you are self-hosting [HCP Terraform agents](/terraform/cloud-docs/agents), ensure your agents use [v1.7.0](/terraform/cloud-docs/agents/changelog#1-7-0-03-02-2023) or above. To use the latest dynamic credentials features, [upgrade your agents to t... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/dynamic-provider-credentials/gcp-configuration.mdx | main | terraform | [
-0.030029457062482834,
-0.009990915656089783,
0.036773573607206345,
-0.02500307559967041,
-0.07973367720842361,
0.0373447947204113,
-0.015966009348630905,
-0.010303276591002941,
0.009367291815578938,
0.04760093241930008,
-0.05075870454311371,
-0.08062147349119186,
0.07805559784173965,
-0.0... | -0.010593 |
\* \*\*Attribute Conditions\*\*: Conditions to restrict which identity tokens can authenticate using the workload identity pool, such as `assertion.sub.startsWith("organization:my-org:project:my-project:workspace:my-workspace")` to restrict access to identity tokens from a specific workspace. See this page in Google do... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/dynamic-provider-credentials/gcp-configuration.mdx | main | terraform | [
-0.08576991409063339,
0.06841079145669937,
0.04861894249916077,
-0.007218607235699892,
0.013842644169926643,
-0.010872653685510159,
0.12632159888744354,
-0.10796792805194855,
-0.0028013105038553476,
0.03270182013511658,
-0.025399338454008102,
-0.13780027627944946,
0.12872089445590973,
0.04... | 0.072267 |
Provider that HCP Terraform will use when authenticating to GCP. You can supply this information in two different ways: 1. By providing one unified variable containing the canonical name of the workload identity provider. 2. By providing the project number, pool ID, and provider ID as separate variables. You should avo... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/dynamic-provider-credentials/gcp-configuration.mdx | main | terraform | [
-0.03741953521966934,
0.044890664517879486,
0.029539745301008224,
-0.02561357244849205,
-0.058122362941503525,
0.06593777239322662,
0.08954271674156189,
-0.0185776986181736,
0.0016544746467843652,
-0.010990954004228115,
-0.0306912362575531,
-0.13697278499603271,
0.08476616442203522,
-0.006... | -0.043238 |
map(object({ credentials = string })) }) } ``` #### Example Usage ```hcl provider "google" { credentials = var.tfc\_gcp\_dynamic\_credentials.default.credentials } provider "google" { alias = "ALIAS1" credentials = var.tfc\_gcp\_dynamic\_credentials.aliases["ALIAS1"].credentials } ``` | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/dynamic-provider-credentials/gcp-configuration.mdx | main | terraform | [
0.021456856280565262,
0.026536820456385612,
0.017562171444296837,
-0.00862535834312439,
-0.13380460441112518,
0.02849709801375866,
0.0886937752366066,
0.11322492361068726,
-0.046806950122117996,
-0.03737100213766098,
-0.008566790260374546,
-0.08611566573381424,
0.019278379157185555,
0.0225... | -0.050663 |
# HCP Vault Secrets-Backed Dynamic Credentials @include 'deprecation/hcp-vault-secrets.mdx' This topic provides an overview of how to use HCP Vault Secrets to generate temporary credentials for providers so that you can securely use them in HCP Terraform runs. ## Introduction Configuring [dynamic provider credentials](... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/dynamic-provider-credentials/hcp-vault-secrets-backed/index.mdx | main | terraform | [
-0.05083262175321579,
0.0445917472243309,
-0.00917322002351284,
-0.06710433214902878,
-0.04923708736896515,
0.055514752864837646,
0.002908213995397091,
-0.014394912868738174,
0.006950192619115114,
-0.01344196405261755,
-0.06430791318416595,
-0.055413130670785904,
0.12954546511173248,
-0.03... | -0.022285 |
# HCP Vault Secrets-Backed Dynamic Credentials with the AWS Provider @include 'deprecation/hcp-vault-secrets.mdx' ~> \*\*Important:\*\* If you are self-hosting [HCP Terraform agents](/terraform/cloud-docs/agents), ensure your agents use [v1.16.0](/terraform/cloud-docs/agents/changelog#1-16-0-10-02-2024) or above. To us... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/dynamic-provider-credentials/hcp-vault-secrets-backed/aws-configuration.mdx | main | terraform | [
-0.0288738664239645,
0.04696391895413399,
-0.003565387800335884,
-0.03956043720245361,
-0.06298679858446121,
0.04740999639034271,
-0.044201020151376724,
-0.00804117415100336,
0.038534194231033325,
0.025816431269049644,
-0.04904527589678764,
-0.05410996079444885,
0.11432220041751862,
-0.023... | -0.05021 |
plan phase. | Requires \*\*v1.16.0\*\* or later if self-managing agents. Must be present. | | `TFC\_HVS\_BACKED\_AWS\_APPLY\_SECRET\_RESOURCE\_NAME` | The name of the HCP Vault Secrets dynamic secret resource to read for the apply phase. | Requires \*\*v1.16.0\*\* or later if self-managing agents. Must be present. | ##... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/dynamic-provider-credentials/hcp-vault-secrets-backed/aws-configuration.mdx | main | terraform | [
0.013078704476356506,
0.08588040620088577,
-0.010454792529344559,
-0.04334360361099243,
-0.030304206535220146,
0.006335501093417406,
-0.032753992825746536,
-0.04066665843129158,
0.0009559807367622852,
0.03360694646835327,
0.004900726955384016,
-0.08521384000778198,
0.056537188589572906,
-0... | -0.045133 |
# HCP Vault Secrets-Backed Dynamic Credentials with the GCP Provider @include 'deprecation/hcp-vault-secrets.mdx' ~> \*\*Important:\*\* If you are self-hosting [HCP Terraform agents](/terraform/cloud-docs/agents), ensure your agents use [v1.16.0](/terraform/cloud-docs/agents/changelog#1-16-0-10-02-2024) or above. To us... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/dynamic-provider-credentials/hcp-vault-secrets-backed/gcp-configuration.mdx | main | terraform | [
-0.02710607647895813,
0.03759664297103882,
0.01668894663453102,
-0.053017809987068176,
-0.07085590809583664,
0.04294147342443466,
-0.03560168296098709,
-0.010969349183142185,
0.023085245862603188,
0.02381637692451477,
-0.047606054693460464,
-0.048833053559064865,
0.10558411478996277,
-0.01... | -0.056455 |
resource to read for the plan phase. | Requires \*\*v1.16.0\*\* or later if self-managing agents. Must be present. | | `TFC\_HVS\_BACKED\_GCP\_APPLY\_SECRET\_RESOURCE\_NAME` | The name of the HCP Vault Secrets dynamic secret resource to read for the apply phase. | Requires \*\*v1.16.0\*\* or later if self-managing agen... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/dynamic-provider-credentials/hcp-vault-secrets-backed/gcp-configuration.mdx | main | terraform | [
-0.03876057267189026,
0.040576864033937454,
0.045209161937236786,
-0.04619014263153076,
-0.0593164898455143,
0.018555743619799614,
-0.005869066342711449,
-0.03195975348353386,
-0.0383080430328846,
0.016311075538396835,
-0.004042056854814291,
-0.0901903286576271,
0.05591633543372154,
-0.012... | -0.063269 |
# Use Vault-backed dynamic credentials ~> \*\*Important:\*\* If you are self-hosting [HCP Terraform agents](/terraform/cloud-docs/agents), ensure your agents use [v1.8.0](/terraform/cloud-docs/agents/changelog#1-8-0-04-18-2023) or above. To use the latest dynamic credentials features, [upgrade your agents to the latest... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/dynamic-provider-credentials/vault-backed/index.mdx | main | terraform | [
-0.05439858138561249,
0.004607635084539652,
-0.017573652788996696,
-0.015610306523740292,
-0.07320541143417358,
-0.0022117337211966515,
-0.029127763584256172,
0.016222454607486725,
0.05731111019849777,
0.01621210016310215,
-0.041645150631666183,
-0.034505173563957214,
0.08393602818250656,
... | -0.05161 |
# Use Vault-backed dynamic credentials with the AWS provider ~> \*\*Important:\*\* If you are self-hosting [HCP Terraform agents](/terraform/cloud-docs/agents), ensure your agents use [v1.8.0](/terraform/cloud-docs/agents/changelog#1-8-0-04-18-2023) or above. To use the latest dynamic credentials features, [upgrade you... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/dynamic-provider-credentials/vault-backed/aws-configuration.mdx | main | terraform | [
-0.013356237672269344,
0.025874756276607513,
-0.023201968520879745,
-0.018944326788187027,
-0.06187427043914795,
0.043659549206495285,
-0.044744186103343964,
0.008301055990159512,
0.04408981651067734,
0.019923273473978043,
-0.048939451575279236,
-0.055438511073589325,
0.11119119822978973,
... | -0.035902 |
`iam\_user`, `assumed\_role`, or `federation\_token`. | Requires \*\*v1.8.0\*\* or later if self-managing agents. | | `TFC\_VAULT\_BACKED\_AWS\_RUN\_VAULT\_ROLE` `TFC\_VAULT\_BACKED\_AWS\_RUN\_VAULT\_ROLE[\_TAG]` `TFC\_DEFAULT\_VAULT\_BACKED\_AWS\_RUN\_VAULT\_ROLE` | The role to use in Vault. | Requires \*\*v1.8.0\*\* ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/dynamic-provider-credentials/vault-backed/aws-configuration.mdx | main | terraform | [
0.08090969175100327,
0.023749426007270813,
-0.07219269871711731,
-0.03416319936513901,
0.036496054381132126,
-0.002198026515543461,
0.027679869905114174,
0.024408139288425446,
0.008095254190266132,
-0.012653740122914314,
0.05212885141372681,
-0.1137455403804779,
0.07475939393043518,
0.0386... | -0.010164 |
data source and any instances of [`vault\_generic\_secret`](https://registry.terraform.io/providers/hashicorp/vault/latest/docs/data-sources/generic\_secret) you previously used to generate AWS credentials. ### Specifying Multiple Configurations ~> \*\*Important:\*\* If you are self-hosting [HCP Terraform agents](/terr... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/dynamic-provider-credentials/vault-backed/aws-configuration.mdx | main | terraform | [
-0.004356941673904657,
0.004895743913948536,
-0.03899636119604111,
-0.035018034279346466,
-0.07194492220878601,
-0.020990492776036263,
-0.04025012254714966,
-0.015410815365612507,
0.05236887186765671,
0.03755047172307968,
-0.01925274357199669,
-0.05468008667230606,
0.09644618630409241,
-0.... | -0.066303 |
# Use Vault-backed dynamic credentials with the Azure provider ~> \*\*Important:\*\* If you are self-hosting [HCP Terraform agents](/terraform/cloud-docs/agents), ensure your agents use [v1.8.0](/terraform/cloud-docs/agents/changelog#1-8-0-04-18-2023) or above. To use the latest dynamic credentials features, [upgrade y... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/dynamic-provider-credentials/vault-backed/azure-configuration.mdx | main | terraform | [
-0.014677748084068298,
0.023284578695893288,
-0.026347260922193527,
-0.007298140786588192,
-0.06694597750902176,
0.06171505153179169,
-0.03206714987754822,
-0.005073490086942911,
0.04359742999076843,
0.039668723940849304,
-0.04413270205259323,
-0.048350170254707336,
0.11449173837900162,
0.... | -0.042711 |
secrets engine in Vault. | Requires \*\*v1.8.0\*\* or later if self-managing agents. Defaults to `azure`. | | `TFC\_VAULT\_BACKED\_AZURE\_PLAN\_VAULT\_ROLE` `TFC\_VAULT\_BACKED\_AZURE\_PLAN\_VAULT\_ROLE[\_TAG]` `TFC\_DEFAULT\_VAULT\_BACKED\_AZURE\_PLAN\_VAULT\_ROLE` | The Vault role to use the plan phase of a run. | Re... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/dynamic-provider-credentials/vault-backed/azure-configuration.mdx | main | terraform | [
0.008593874052166939,
0.006623541004955769,
-0.08295412361621857,
0.020250605419278145,
-0.006750490516424179,
0.030813589692115784,
-0.021678650751709938,
-0.017681214958429337,
0.03642488270998001,
0.0011127752950415015,
0.03745555132627487,
-0.03748169168829918,
0.02981547638773918,
0.0... | -0.017075 |
{} // use\_cli should be set to false to yield more accurate error messages on auth failure. use\_cli = false alias = "ALIAS1" client\_id\_file\_path = var.tfc\_vault\_backed\_azure\_dynamic\_credentials.aliases["ALIAS1"].client\_id\_file\_path client\_secret\_file\_path = var.tfc\_vault\_backed\_azure\_dynamic\_creden... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/dynamic-provider-credentials/vault-backed/azure-configuration.mdx | main | terraform | [
-0.000030313651222968474,
0.06909623742103577,
-0.0447988323867321,
-0.04680521413683891,
-0.02381027676165104,
-0.025033636018633842,
0.1004154309630394,
0.034204013645648956,
0.06810811907052994,
0.01944761537015438,
0.028894806280732155,
-0.1029471606016159,
0.11597225069999695,
0.04858... | -0.094044 |
# Use Vault-backed dynamic credentials with the GCP provider ~> \*\*Important:\*\* If you are self-hosting [HCP Terraform agents](/terraform/cloud-docs/agents), ensure your agents use [v1.8.0](/terraform/cloud-docs/agents/changelog#1-8-0-04-18-2023) or above. To use the latest dynamic credentials features, [upgrade you... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/dynamic-provider-credentials/vault-backed/gcp-configuration.mdx | main | terraform | [
-0.02654711715877056,
0.006952290423214436,
0.0136686647310853,
-0.030808662995696068,
-0.07670937478542328,
0.04163061082363129,
-0.03417496010661125,
0.00007958253991091624,
0.01808142475783825,
0.022356098517775536,
-0.04438337683677673,
-0.04917379096150398,
0.09597261995077133,
-0.011... | -0.042599 |
`roleset/access\_token`, `roleset/service\_account\_key`, `static\_account/access\_token`, or `static\_account/service\_account\_key`. | Requires \*\*v1.8.0\*\* or later if self-managing agents. | #### Optional Common Environment Variables You may need to set these variables, depending on your use case. | Variable | Va... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/dynamic-provider-credentials/vault-backed/gcp-configuration.mdx | main | terraform | [
0.015309949405491352,
-0.0066412403248250484,
-0.09369704872369766,
-0.004825230222195387,
-0.06943754851818085,
0.02597745880484581,
0.05151655152440071,
0.06527311354875565,
-0.05402242764830589,
-0.020129231736063957,
0.06619540601968765,
-0.06470219045877457,
0.053947459906339645,
0.00... | 0.031025 |
Terraform agents](/terraform/cloud-docs/agents), ensure your agents use [v1.12.0](/terraform/cloud-docs/agents/changelog#1-12-0-07-26-2023) or above. To use the latest dynamic credentials features, [upgrade your agents to the latest version](/terraform/cloud-docs/agents/changelog). You can add additional variables to h... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/dynamic-provider-credentials/vault-backed/gcp-configuration.mdx | main | terraform | [
0.0035637167748063803,
-0.041728388518095016,
-0.021804528310894966,
-0.05438597872853279,
-0.10153522342443466,
0.019561009481549263,
0.004529785830527544,
-0.023635191842913628,
0.02270197495818138,
0.01348918117582798,
-0.012297543697059155,
-0.06808865070343018,
0.10864027589559555,
0.... | -0.078375 |
# Use HCP Terraform in Europe HashiCorp's product-as-a-service platform, [HashiCorp Cloud Platform (HCP)](/hcp/docs), can manage infrastructure in Europe. With HCP Europe, your resources are hosted, managed, and billed separately to meet [European data residency requirements](https://www.hashicorp.com/en/trust/privacy/... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/europe/index.mdx | main | terraform | [
0.05337812751531601,
0.016918368637561798,
-0.02135590650141239,
-0.0813668966293335,
0.004178326111286879,
-0.04891754686832428,
-0.02373744547367096,
-0.03945257514715195,
0.002377146854996681,
-0.010653143748641014,
-0.0005531204515136778,
-0.08223360776901245,
0.007884361781179905,
0.0... | 0.108324 |
[private module registry]: /terraform/cloud-docs/registry [policy sets]: /terraform/cloud-docs/policy-enforcement/manage-policy-sets [vcs settings]: /terraform/cloud-docs/workspaces/settings/vcs [create]: /terraform/cloud-docs/workspaces/create [owners]: /terraform/cloud-docs/users-teams-organizations/teams#the-owners-... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/vcs/github-app.mdx | main | terraform | [
-0.0624321848154068,
-0.027467871084809303,
-0.029925772920250893,
-0.0034678212832659483,
-0.056901127099990845,
-0.012020329013466835,
-0.042602285742759705,
-0.014500314369797707,
0.07006482779979706,
0.03799743205308914,
0.004966938868165016,
-0.018498552963137627,
0.050828706473112106,
... | 0.045007 |
App and creating your VCS provider instance, you cannot reinstall the application again. However, you can modify your existing GitHub App configuration. If you are a repository owner, you can adjust an existing Github App configuration by: 1. Click a repository's \*\*Settings\*\* tab. 1. Select \*\*GitHub Apps\*\* in t... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/vcs/github-app.mdx | main | terraform | [
-0.0264715738594532,
-0.07249684631824493,
0.019246477633714676,
-0.0337534174323082,
-0.03907305747270584,
0.03186699375510216,
-0.06726948916912079,
-0.046734392642974854,
0.0566449910402298,
0.0725901871919632,
-0.008187511004507542,
-0.0006640686769969761,
0.0636381283402443,
-0.021408... | -0.040347 |
Feature Limitations You can use the Terraform Cloud GitHub App to create workspaces and private registry modules from the UI, the API, or the TFE Terraform provider. The following tools can use any version of HCP Terraform to access these features, but require a minimum version of Terraform Enterprise: - For the UI, us... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/vcs/github-app.mdx | main | terraform | [
0.0009815129451453686,
-0.017407003790140152,
-0.03217194974422455,
-0.04052095115184784,
-0.04130784794688225,
-0.02297431044280529,
-0.06739039719104767,
-0.008286899887025356,
-0.0024422607384622097,
0.024113716557621956,
0.00471201678737998,
-0.06258264183998108,
0.009143592789769173,
... | 0.089655 |
# Set up the GitLab.com VCS provider These instructions describe how to connect to GitLab.com. Refer to [GitLab EE](/terraform/cloud-docs/vcs/gitlab-eece) for instructions on connecting to GitLab EE. Refer to [VCS overview](/terraform/cloud-docs/vcs) for information about abll VCS integrations. ## Overview Complete the... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/vcs/gitlab-com.mdx | main | terraform | [
-0.039296042174100876,
0.020853614434599876,
0.01533493772149086,
-0.03035505674779415,
-0.08556158095598221,
-0.056066855788230896,
-0.027094298973679543,
-0.013574616983532906,
0.026025736704468727,
0.006624245084822178,
-0.06577416509389877,
-0.06806191056966782,
0.09926369041204453,
-0... | -0.022112 |
VCS Provider\*\* - You can configure which workspaces or Stacks can use repositories from this VCS provider. By default the \*\*All Projects\*\* option is selected, meaning this VCS provider is available to be used by all workspaces and Stacks in the organization. - \*\*Set up SSH Keypair\*\* - Most organizations will ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/vcs/gitlab-com.mdx | main | terraform | [
-0.03631263226270676,
-0.07971912622451782,
-0.044332798570394516,
-0.024393709376454353,
-0.08165837824344635,
-0.018178440630435944,
-0.02264798991382122,
-0.022389423102140427,
0.06694821268320084,
0.027354251593351364,
0.02532786875963211,
-0.05249524861574173,
0.09014347940683365,
0.0... | -0.023601 |
# 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 |
repositories 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 tha... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/vcs/index.mdx | main | terraform | [
-0.055101439356803894,
-0.0049268947914242744,
0.03195461630821228,
-0.01819000206887722,
-0.005891116335988045,
-0.009616690687835217,
-0.06065107136964798,
-0.04896417632699013,
0.07041207700967789,
0.10069939494132996,
-0.023793837055563927,
-0.03819577768445015,
0.004926758352667093,
-... | 0.053408 |
\*\*Important:\*\* Even if 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... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/vcs/index.mdx | main | terraform | [
-0.021079203113913536,
0.04416600987315178,
0.025265133008360863,
-0.07540182024240494,
-0.02704184502363205,
-0.01266412902623415,
-0.015042751096189022,
-0.0277814082801342,
0.05140175297856331,
-0.022685308009386063,
-0.03791530057787895,
-0.07239846885204315,
0.06120527908205986,
-0.05... | -0.054035 |
# 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 |
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.03654342517256737,
-0.12390349805355072,
-0.07639172673225403,
0.00010394978744443506,
-0.02045043185353279,
-0.05232246592640877,
-0.06593845784664154,
0.03530143201351166,
0.011912701651453972,
0.005909539293497801,
0.048730045557022095,
0.04711546376347542,
-0.0488467663526535,
0.033... | 0.184482 |
# 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.01836523972451687,
-0.020311657339334488,
-0.014817570336163044,
-0.027323275804519653,
-0.0742049589753151,
0.04065718874335289,
-0.052962806075811386,
-0.034591998904943466,
-0.01185113750398159,
0.08402133733034134,
-0.0020843700040131807,
-0.09512395411729813,
0.06418030709028244,
-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.07391350716352463,
0.01510696206241846,
0.06728809326887131,
-0.01044012513011694,
0.008839042857289314,
-0.007636372931301594,
-0.06178536266088486,
-0.07936704903841019,
0.03189407289028168,
0.06604129076004028,
0.006796852685511112,
-0.11424660682678223,
-0.000851709337439388,
-0.0015... | -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.03457295522093773,
0.04010310769081116,
0.03111748956143856,
0.06691562384366989,
-0.03810364753007889,
0.04213295504450798,
0.05782947689294815,
-0.09028173983097076,
-0.001754780183546245,
0.08941546082496643,
-0.035778697580099106,
-0.044091690331697464,
0.058564744889736176,
-0.01752... | -0.013488 |
to specific workspaces and Stacks in the project:\*\* Use the text fields to search for and select workspaces and Stacks to apply this variable set to. After creation, users can also [add this variable set to their workspaces](#apply-or-remove-variable-sets-from-inside-a-workspace). 1. Add one or more variables: Click ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/terraform-docs-common/docs/cloud-docs/variables/managing-variables.mdx | main | terraform | [
0.006153840571641922,
-0.021831519901752472,
-0.00741598941385746,
0.05899845436215401,
-0.0669039785861969,
0.027482302859425545,
0.019099880009889603,
-0.061431679874658585,
-0.034115202724933624,
0.06229473277926445,
-0.005719946697354317,
-0.12874041497707367,
0.07884716242551804,
-0.0... | -0.023452 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.