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 |
|---|---|---|---|---|---|
true monorepos, as it queues unnecessary runs and slows down your ability to provision infrastructure. #### Only trigger runs when files in specified paths change This option instructs Terraform to begin new runs only for changes that affect specified files and directories. This behavior also applies to [speculative pl... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/settings/vcs.mdx | main | terraform | [
-0.06561760604381561,
-0.034824978560209274,
0.10573819279670715,
0.012133646756410599,
-0.01037499401718378,
-0.0682128518819809,
-0.057217858731746674,
-0.04948437213897705,
0.05793313309550285,
0.12407990545034409,
-0.012505787424743176,
-0.04354778304696083,
-0.004438750445842743,
-0.0... | 0.055815 |
Speculative Plans Whether to perform [speculative plans on pull requests](/terraform/cloud-docs/workspaces/run/ui#speculative-plans-on-pull-requests) to the connected repository, to assist in reviewing proposed changes. Automatic speculative plans are enabled by default, but you can disable them for any workspace. ### ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/settings/vcs.mdx | main | terraform | [
-0.051744502037763596,
-0.017603304237127304,
0.06563445925712585,
-0.01462196558713913,
0.0122119951993227,
-0.058607131242752075,
-0.0028557227924466133,
-0.05497606843709946,
0.0161319300532341,
0.045749738812446594,
0.005205671302974224,
-0.03749481588602066,
0.0326400026679039,
-0.041... | 0.042137 |
[entitlement]: /terraform/cloud-docs/api-docs#feature-entitlements # Run tasks HCP Terraform run tasks let you directly integrate third-party tools and services at certain stages in the HCP Terraform run lifecycle. Use run tasks to validate Terraform configuration files, analyze execution plans before applying them, sc... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/settings/run-tasks.mdx | main | terraform | [
-0.016961049288511276,
-0.0011518315877765417,
0.003663755487650633,
-0.05250461772084236,
-0.007576661184430122,
-0.020728781819343567,
-0.0660528689622879,
-0.026410723105072975,
-0.007950610481202602,
0.05151963606476784,
-0.04318154975771904,
-0.08521123230457306,
0.06135213002562523,
... | 0.069933 |
feature. To enforce a run task globally to every workspace, your organization must have the `global-run-task` [entitlement][] to use global run tasks. To scope a run task to your organization or projects, complete the following steps: 1. Sign in to [HCP Terraform](https://app.terraform.io/) and navigate to your organiz... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/settings/run-tasks.mdx | main | terraform | [
-0.016914600506424904,
-0.023469103500247,
0.02813679352402687,
0.003010565647855401,
-0.033174801617860794,
-0.01971897855401039,
-0.060477111488580704,
-0.0796850323677063,
-0.04030328989028931,
0.09769880771636963,
-0.08771326392889023,
-0.09025043994188309,
0.06398577243089676,
0.03344... | 0.017784 |
1. Choose \*\*Settings\*\* from the sidebar, then \*\*Run Tasks\*\*. 1. Click the ellipsis (\*\*...\*\*) next to the run task you want to remove, and then click \*\*Remove\*\*. When prompted, click \*\*Remove\*\* to confirm the removal. The run task will no longer be applied to runs within the workspace. ## Delete a ru... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/settings/run-tasks.mdx | main | terraform | [
-0.010830581188201904,
0.03279002010822296,
0.02795408107340336,
0.010570078156888485,
0.012288137339055538,
-0.05022525414824486,
-0.010540852323174477,
-0.10551510006189346,
0.02703126333653927,
0.0827479213476181,
-0.07931235432624817,
-0.025632048025727272,
0.043720781803131104,
-0.017... | 0.049502 |
# GCP resources included in cost estimation HCP Terraform can estimate monthly costs for many GCP Terraform resources. -> \*\*Note:\*\* Terraform Enterprise requires GCP credentials to support cost estimation. These credentials are configured at the instance level, not the organization level. See the [Application Admin... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/cost-estimation/gcp.mdx | main | terraform | [
-0.026868298649787903,
-0.054063521325588226,
0.027280807495117188,
0.013313006609678268,
-0.0492006279528141,
-0.01882658526301384,
0.02735494263470173,
-0.044250424951314926,
-0.029882410541176796,
0.06860684603452682,
-0.0477617047727108,
-0.1480909287929535,
0.07914625108242035,
-0.015... | 0.021295 |
# AWS resources included in cost estimation HCP Terraform can estimate monthly costs for many AWS Terraform resources. -> \*\*Note:\*\* Terraform Enterprise requires AWS credentials to support cost estimation. These credentials are configured at the instance level, not the organization level. See the [Application Admin... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/cost-estimation/aws.mdx | main | terraform | [
-0.004047076683491468,
0.0060239313170313835,
-0.0326266847550869,
0.024434098973870277,
0.010256864130496979,
0.004688901361078024,
0.004998968448489904,
-0.04830693453550339,
0.042820725589990616,
0.07045062631368637,
-0.07163330167531967,
-0.16418646275997162,
0.11306688189506531,
-0.04... | 0.040259 |
| `aws\_s3\_bucket\_public\_access\_block` | | | `aws\_security\_group` | | | `aws\_security\_group\_rule` | | | `aws\_service\_discovery\_service` | | | `aws\_sfn\_state\_machine` | | | `aws\_sns\_topic` | | | `aws\_sns\_topic\_subscription` | | | `aws\_sqs\_queue` | | | `aws\_sqs\_queue\_policy` | | | `aws\_ssm\_main... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/cost-estimation/aws.mdx | main | terraform | [
-0.007586939260363579,
-0.03574264422059059,
-0.10996222496032715,
-0.0060491859912872314,
0.06049330160021782,
-0.01926915906369686,
0.08510826528072357,
-0.07860792428255081,
0.08257487416267395,
0.0711645632982254,
0.03924620896577835,
-0.019803009927272797,
0.06963642686605453,
-0.0099... | 0.065168 |
# Cost estimation overview HCP Terraform provides cost estimates for many resources found in your Terraform configuration. For each resource an hourly and monthly cost is shown, along with the monthly delta. The total cost and delta of all estimable resources is also shown. ## Enabling Cost Estimation HCP Terraform dis... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/cost-estimation/index.mdx | main | terraform | [
0.014419727958738804,
0.02319350093603134,
0.011799476109445095,
0.04957189783453941,
-0.004785711877048016,
-0.030981386080384254,
-0.04155623912811279,
-0.04128878563642502,
0.022761080414056778,
0.08334432542324066,
-0.0784752294421196,
-0.1501104086637497,
0.04769834131002426,
-0.03303... | 0.054046 |
# Azure resources included in cost estimation HCP Terraform can estimate monthly costs for many Azure Terraform resources. -> \*\*Note:\*\* Terraform Enterprise requires Azure credentials to support cost estimation. These credentials are configured at the instance level, not the organization level. See the [Application... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/cost-estimation/azure.mdx | main | terraform | [
0.01508402731269598,
-0.0062492904253304005,
-0.024853069335222244,
0.03723170608282089,
-0.03611459955573082,
0.0265312772244215,
0.013640671968460083,
-0.04261116310954094,
0.021352574229240417,
0.10147374123334885,
-0.07807710766792297,
-0.14529705047607422,
0.10249660164117813,
0.01010... | 0.026683 |
# Change requests overview Change requests are a way to create a backlog of action items recorded on a workspace, enabling administrators to notify teams directly if a workspace requires action. Workspace action items can include updating [deprecated or revoked module versions](/terraform/cloud-docs/registry/manage-mod... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/change-requests/index.mdx | main | terraform | [
-0.039306171238422394,
0.006861160043627024,
0.05950530245900154,
0.014494634233415127,
0.04377732798457146,
-0.01862163282930851,
0.0031245159916579723,
-0.08379621803760529,
0.054158903658390045,
0.10752693563699722,
-0.06702069193124771,
-0.01480975840240717,
-0.03928272798657417,
0.000... | 0.044215 |
# Manage change requests This topic describes how to create and manage change requests. Refer to [Change requests overview](/terraform/cloud-docs/workspaces/change-requests) for additional information about change requests. @include 'tfc-package-callouts/change-requests.mdx' ## Requirements To create a change request y... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/change-requests/manage.mdx | main | terraform | [
-0.03088601492345333,
-0.01155967265367508,
0.036181848496198654,
-0.021987320855259895,
-0.011586455628275871,
-0.05530555918812752,
-0.05347425118088722,
-0.06956975162029266,
0.04651441425085068,
0.13565054535865784,
-0.07300121337175369,
-0.07955659925937653,
-0.011894091963768005,
0.0... | -0.008779 |
request on others. To archive a change request in a workspace, perform the following steps: 1. Navigate to a workspace’s \*\*Change requests\*\* page. 1. Click on the ellipsis menu next to a change request. 1. Click \*\*Archive\*\*. You can also archive a change request by navigating to a workspace’s \*\*Change request... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/change-requests/manage.mdx | main | terraform | [
-0.09492932260036469,
-0.015033592469990253,
-0.010161783546209335,
0.011368476785719395,
0.039500344544649124,
-0.012369239702820778,
-0.0698542520403862,
-0.12089277803897858,
0.046187881380319595,
0.05099991336464882,
-0.08749255537986755,
0.06058153137564659,
-0.021383777260780334,
-0.... | 0.025008 |
# HCP Terraform policy enforcement overview This topic provides overview information about policies in HCP Terraform. Policies are rules for Terraform runs that let you validate that Terraform plans comply with security rules and best practices. @include 'tfc-package-callouts/policies.mdx' > \*\*Hands-on:\*\* Try the [... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/index.mdx | main | terraform | [
-0.02500007674098015,
0.05881861224770546,
0.06270284205675125,
-0.07380014657974243,
0.011195610277354717,
-0.05677070841193199,
-0.0031416763085871935,
-0.0672978088259697,
-0.0660315454006195,
0.07419275492429733,
-0.03560521826148033,
-0.049662236124277115,
0.04303963482379913,
0.00625... | 0.081282 |
# Pre-written policy library reference This topic provides reference information about the Sentinel policy libraries that HashiCorp authors and maintains. For instructions on how to run the policy libraries, refer to [Run pre-written Sentinel policies ](/terraform/cloud-docs/policy-enforcement/prewritten-sentinel). ## ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/prewritten-library.mdx | main | terraform | [
-0.014149153605103493,
0.002612812677398324,
-0.0416770875453949,
-0.015596630983054638,
0.04469088837504387,
-0.052951786667108536,
-0.022696493193507195,
-0.00527274701744318,
0.016000015661120415,
0.07578550279140472,
0.003191250143572688,
0.011400575749576092,
0.02109568379819393,
-0.0... | 0.199251 |
# Generate mock Sentinel data with Terraform We recommend that you test your Sentinel policies extensively before deploying them within HCP Terraform. An important part of this process is mocking the data that you wish your policies to operate on. @include 'tfc-package-callouts/policies.mdx' Due to the highly variable ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/test-sentinel.mdx | main | terraform | [
-0.0013211843324825168,
0.02046222798526287,
0.02798341028392315,
-0.005517049692571163,
0.0005962333525530994,
-0.057463403791189194,
-0.012860278598964214,
-0.07417743653059006,
-0.07515431195497513,
0.06668096035718918,
-0.010293226689100266,
-0.08730807900428772,
0.06535736471414566,
-... | 0.06792 |
with the command's automatic policy detection. While the test data is Sentinel code, it's not a policy and will produce errors if evaluated like one. ``` . ├── foo.sentinel ├── sentinel.hcl ├── test │ └── foo │ ├── fail.hcl │ └── pass.hcl └── testdata ├── mock-tfconfig.sentinel ├── mock-tfconfig-v2.sentinel ├── mock-tf... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/test-sentinel.mdx | main | terraform | [
-0.016863344237208366,
-0.04150024801492691,
-0.03468893840909004,
0.04339000582695007,
0.037535347044467926,
-0.03778430074453354,
0.018017370253801346,
0.04014632850885391,
-0.0381653718650341,
0.014780577272176743,
0.0546095110476017,
-0.08482716232538223,
0.03294201195240021,
0.0008871... | 0.062699 |
# Run pre-written Sentinel policies This topic describes how to run Sentinel policies created and maintained by HashiCorp. For instructions about how to create your own custom Sentinel policies, refer to [Define custom Sentinel policies](/terraform/cloud-docs/policy-enforcement/define-policies/custom-sentinel). ## Over... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/prewritten-sentinel.mdx | main | terraform | [
0.03832034394145012,
-0.002399500459432602,
0.015239323489367962,
-0.03061717376112938,
0.011030412279069424,
-0.019368531182408333,
-0.032744575291872025,
-0.03014359250664711,
-0.04003585875034332,
0.08557140827178955,
-0.016968321055173874,
-0.05486011505126953,
0.01815694011747837,
-0.... | 0.111457 |
a new policy set\*\*. 1. Click the \*\*Version control provider (VCS)\*\* tile. 1. Enable the \*\*Sentinel\*\* option as the policy framework. 1. Specify a name and description for the set. 1. Configure any additional options for the policy set and click \*\*Next\*\*. 1. Choose the GitHub connection type, then choose t... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/prewritten-sentinel.mdx | main | terraform | [
0.006422447506338358,
-0.10447866469621658,
-0.05207598954439163,
0.03285585716366768,
-0.025737673044204712,
0.031912606209516525,
-0.012425481341779232,
-0.019352689385414124,
-0.028700171038508415,
0.08172620087862015,
-0.022706054151058197,
-0.033485427498817444,
-0.0018335938220843673,
... | 0.095875 |
# View and filter Sentinel JSON data When using the HCP Terraform UI, Sentinel policy check results are available both in a human-readable log form, and in a more detailed, lower-level JSON form. While the logs may suppress some output that would make the logs harder to read, the JSON output exposes the lower-level out... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/view-results/json.mdx | main | terraform | [
0.016420042142271996,
0.062107134610414505,
0.04901578649878502,
-0.03834172710776329,
0.07217849045991898,
-0.020402319729328156,
0.016772277653217316,
-0.0668395385146141,
0.03230086714029312,
0.0783185064792633,
-0.014189183712005615,
-0.050988782197237015,
0.0038819736801087856,
0.0391... | 0.036465 |
# View policy enforcement results When you add [policy sets](/terraform/cloud-docs/policy-enforcement/manage-policy-sets) to a workspace, HCP Terraform enforces those policy sets on every Terraform run. HCP Terraform displays the policy enforcement results in the UI for each run. Depending on each policy’s [enforcement... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/view-results/index.mdx | main | terraform | [
0.013974086381494999,
0.043668996542692184,
0.05711255967617035,
-0.022489625960588455,
0.03233829140663147,
-0.019513852894306183,
-0.004319616127759218,
-0.05613379925489426,
0.014130190014839172,
0.06527642160654068,
-0.04999653622508049,
-0.0692121833562851,
0.05202905833721161,
-0.018... | 0.038919 |
Terraform displays a warning in the policy results and the run continues. You can override `mandatory` policies to allow the run to continue. | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/view-results/index.mdx | main | terraform | [
0.026020914316177368,
0.010740438476204872,
0.042742013931274414,
0.021259821951389313,
0.04837614670395851,
-0.05041501298546791,
-0.08881402015686035,
-0.12225441634654999,
0.004770640749484301,
0.0684119313955307,
-0.04739873483777046,
-0.007365591358393431,
0.006967212539166212,
0.0036... | -0.037644 |
# Manage policies and policy sets in HCP Terraform Policies are rules that HCP Terraform enforces on Terraform runs. You can define policies using either the [Sentinel](/terraform/cloud-docs/policy-enforcement/define-policies/custom-sentinel) or [Open Policy Agent (OPA)](/terraform/cloud-docs/policy-enforcement/opa) po... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/manage-policy-sets/index.mdx | main | terraform | [
-0.009692602790892124,
0.021637700498104095,
0.03440936282277107,
-0.04977485537528992,
0.04560866951942444,
-0.001691094832494855,
0.0011995868990197778,
-0.07029709219932556,
0.0038522696122527122,
0.04433854669332504,
-0.029630610719323158,
-0.0326869934797287,
0.05982312187552452,
-0.0... | 0.075066 |
be overridden in the event of mandatory failures\*\* option. Enabling this option lets users with the appropriate permissions, such as admins or team owners, override any failed policy checks in that set, even policies set to \*\*Hard mandatory\*\*. This override setting takes precedence over the individual policy’s en... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/manage-policy-sets/index.mdx | main | terraform | [
-0.008234105072915554,
0.040379732847213745,
0.0565839521586895,
0.014649694785475731,
-0.01010123174637556,
-0.06451166421175003,
-0.02632591500878334,
-0.05388690531253815,
-0.028517285361886024,
0.10291578620672226,
-0.030506299808621407,
-0.022578496485948563,
0.036208655685186386,
0.0... | -0.02563 |
\*\*(Optional) Policy sets:\*\* Select one or more existing managed policy sets where you want to add the new policy. You can only select policy sets compatible with the chosen policy set framework. If there are no policy sets available, you can [create a new one](#create-policy-sets). The policy is now available in th... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/manage-policy-sets/index.mdx | main | terraform | [
0.012739438563585281,
0.02311571314930916,
0.033805351704359055,
-0.013443171046674252,
-0.0006413094233721495,
0.031929727643728256,
-0.0033385588321834803,
-0.07409388571977615,
-0.07617507874965668,
0.14833295345306396,
-0.038639672100543976,
-0.07492130994796753,
0.06374473869800568,
-... | -0.003442 |
# Configure a Sentinel policy set with a VCS repository To enable policy enforcement, you must group Sentinel policies into policy sets. You can then apply those policy sets globally or to specific [projects](/terraform/cloud-docs/projects/manage) and workspaces. @include 'tfc-package-callouts/policies.mdx' One way to ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/manage-policy-sets/sentinel-vcs.mdx | main | terraform | [
-0.0014656811254099011,
-0.0341072753071785,
0.013395879417657852,
-0.05015052855014801,
-0.0005655868444591761,
0.032689157873392105,
0.009097123518586159,
-0.055672917515039444,
-0.0020073093473911285,
0.07131915539503098,
-0.03622801974415779,
-0.060594797134399414,
0.05117619037628174,
... | 0.047808 |
false, the rule is not evaluated and returns true. Finally, the example uses parameters to facilitate module reuse within Terraform. Refer to the [Sentinel parameter documentation](/sentinel/docs/language/parameters) for details. ```hcl import "time" import "tfrun" import "timezone" param token default "WbNKULOBheqV" p... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/manage-policy-sets/sentinel-vcs.mdx | main | terraform | [
-0.012414602562785149,
0.01506882719695568,
0.06429408490657806,
0.04367939382791519,
0.0414905920624733,
-0.038659434765577316,
0.038212019950151443,
-0.006927721668034792,
-0.026568276807665825,
0.0525888092815876,
-0.06858217716217041,
-0.09649887681007385,
-0.013147898949682713,
0.0138... | 0.086828 |
# Configure an OPA policy set with a VCS repository To enable policy enforcement, you must group OPA policies into policy sets and apply those policy sets globally or to specific [projects](/terraform/cloud-docs/projects/manage) and workspaces. > \*\*Hands-on:\*\* Try the [Detect Infrastructure Drift and Enforce OPA Po... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/manage-policy-sets/opa-vcs.mdx | main | terraform | [
-0.026194589212536812,
0.00785592757165432,
0.06667562574148178,
-0.053536612540483475,
-0.022806894034147263,
-0.05880415067076683,
-0.009939100593328476,
-0.06927427649497986,
0.017486434429883957,
0.0720740556716919,
-0.007397790439426899,
-0.047668829560279846,
0.028799613937735558,
-0... | 0.012282 |
# Configure connections to policy sets Policy sets are collections of policies that you can apply to an entire organization or to specific projects and workspaces. For more information about defining policies, refer to [Define policies](/terraform/cloud-docs/workspaces/policy-enforcement/define-policies). For informati... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/manage-policy-sets/configure.mdx | main | terraform | [
0.014699217863380909,
-0.007486041635274887,
0.007320198696106672,
-0.03066794015467167,
-0.005588451400399208,
-0.0027768495492637157,
-0.003234479809179902,
-0.047822006046772,
-0.02218785509467125,
0.07139908522367477,
-0.023958897218108177,
-0.033253539353609085,
0.027633026242256165,
... | 0.110764 |
\*\*Policies enforced on selected projects and workspaces\*\* option to enforce the policy set on specific workspaces or all workspaces in project. This affects all current and future workspaces for any projects you choose. 1. For Sentinal policy sets, choose a policy execution mode. Refer to [Policy set execution mode... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/manage-policy-sets/configure.mdx | main | terraform | [
-0.031043393537402153,
0.027875717729330063,
0.08318936079740524,
0.005236439406871796,
0.010910166427493095,
-0.08277667313814163,
-0.000620094477199018,
-0.07910730689764023,
0.029400577768683434,
0.13431358337402344,
-0.019088514149188995,
-0.009325220249593258,
0.008516737259924412,
-0... | -0.040476 |
the same agent instance to evaluate policies and run Terraform operations. When the workspace execution mode is set to \*\*Local\*\* or \*\*Remote\*\*, HCP Terraform or Terraform Enterprise starts a new agent to evaluate the policy. You can explicitly set your workspace execution mode to \*\*Agent\*\* or configure your... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/manage-policy-sets/configure.mdx | main | terraform | [
0.035092491656541824,
0.014656360261142254,
0.006136576645076275,
0.05170809477567673,
-0.014704813249409199,
-0.0236057136207819,
-0.01052477303892374,
-0.037185367196798325,
0.016527319326996803,
0.08089258521795273,
-0.0419369600713253,
-0.0945989117026329,
0.017528772354125977,
0.01123... | 0.035789 |
\*\*Yes, delete policy set\*\* to confirm. The policy set no longer appears on the UI and HCP Terraform no longer applies it to any workspaces. For managed policy sets, all of the individual policies are still available in HCP Terraform. You must delete each policy individually to remove it from your organization. ### ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/manage-policy-sets/configure.mdx | main | terraform | [
-0.007558831479400396,
0.05203072354197502,
0.0035939072258770466,
0.047125812619924545,
-0.0024508601054549217,
0.03152132406830788,
0.062071263790130615,
-0.10735989362001419,
-0.017022812739014626,
0.04570436477661133,
-0.02592482976615429,
-0.06717228889465332,
0.05686940625309944,
-0.... | 0.081421 |
-> \*\*Note:\*\* This is documentation for the next version of the `tfstate` Sentinel import, designed specifically for Terraform 0.12. This import requires Terraform 0.12 or higher, and must currently be loaded by path, using an alias, example: `import "tfstate/v2" as tfstate`. # tfstate/v2 Sentinel import The `tfstat... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/import-reference/tfstate-v2.mdx | main | terraform | [
-0.029476070776581764,
-0.015151423402130604,
0.015326186083257198,
-0.025310110300779343,
0.03925075754523277,
-0.006940439809113741,
0.04303285479545593,
-0.039112161844968796,
0.002719488460570574,
0.03575166314840317,
-0.03783399611711502,
-0.06418929994106293,
0.016313211992383003,
-0... | 0.154162 |
with pre-release versions (example: `0.12.0beta1`). Future versions of this import will include helpers to assist with processing versions that will account for these kinds of exceptions. ## The `resources` Collection The `resources` collection is a collection representing all of the resources in the state, across all ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/import-reference/tfstate-v2.mdx | main | terraform | [
-0.05141504481434822,
0.02091391570866108,
-0.016470029950141907,
0.05307997390627861,
0.08398152142763138,
-0.04301143437623978,
0.01878119632601738,
-0.0379675067961216,
0.006943580228835344,
-0.013283561915159225,
0.022884301841259003,
-0.022602658718824387,
0.10087119042873383,
-0.0526... | 0.047552 |
# tfrun Sentinel import reference The `tfrun` import provides access to data associated with a [Terraform run][run-glossary]. @include 'tfc-package-callouts/policies.mdx' This import currently consists of run attributes, as well as namespaces for the `organization`, `workspace` and `cost-estimate`. Each namespace provi... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/import-reference/tfrun.mdx | main | terraform | [
-0.034029409289360046,
0.0008736985619179904,
0.021001648157835007,
-0.00248105195350945,
-0.02726253680884838,
-0.030852241441607475,
0.05031345412135124,
-0.04953046143054962,
0.023016231134533882,
0.08414127677679062,
-0.010921608656644821,
-0.12530043721199036,
0.023779090493917465,
-0... | 0.132639 |
the `replace-addrs` attribute in the API. Will be null if no resource targets are specified. ### Value: `speculative` \* \*\*Value Type:\*\* Boolean. Specifies whether the plan associated with the run is a [speculative plan](/terraform/cloud-docs/workspaces/run/remote-operations#speculative-plans) only. ### Value: `tar... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/import-reference/tfrun.mdx | main | terraform | [
-0.01809627376496792,
0.030520213767886162,
0.04901162534952164,
-0.01889745332300663,
0.019804339855909348,
-0.06676195561885834,
0.01097145862877369,
-0.10204111784696579,
0.020525721833109856,
0.040195271372795105,
-0.01925910823047161,
-0.11611612886190414,
0.04060082882642746,
-0.0181... | -0.006121 |
### Value: `vcs\_repo` \* \*\*Value Type:\*\* A string-keyed map of values. Contains data associated with a VCS repository connected to the workspace. Details regarding each attribute can be found in the documentation for the HCP Terraform [Workspaces API](/terraform/cloud-docs/api-docs/workspaces). This value can be `... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/import-reference/tfrun.mdx | main | terraform | [
-0.005882018245756626,
0.05280306935310364,
0.01876404881477356,
0.043744321912527084,
-0.016691699624061584,
0.005265553016215563,
0.019823379814624786,
-0.03040136955678463,
0.02964256890118122,
0.08166410773992538,
-0.024929052218794823,
-0.16929173469543457,
0.10123056173324585,
-0.044... | 0.06284 |
# tfconfig Sentinel import ~> \*\*Warning:\*\* The `tfconfig` import is now deprecated and will be permanently removed in August 2025. We recommend that you start using the updated [tfconfig/v2](/terraform/cloud-docs/policy-enforcement/import-reference/tfconfig-v2) import as soon as possible to avoid disruptions. The `... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/import-reference/tfconfig.mdx | main | terraform | [
-0.02689613774418831,
-0.014453859999775887,
0.018468255177140236,
-0.020745260640978813,
0.06009069085121155,
-0.008242922835052013,
0.007745780050754547,
-0.03890826553106308,
0.00635113101452589,
0.048501066863536835,
0.003489350201562047,
-0.05377423018217087,
0.0050857397727668285,
0.... | 0.087235 |
├── config (map of keys) │ │ ├── references (map of keys) (TF 0.12 and later) │ │ └── provisioners │ │ └── NUMBER │ │ ├── config (map of keys) │ │ ├── references (map of keys) (TF 0.12 and later) │ │ └── type (string) │ └── variables │ └── NAME │ ├── default (value) │ └── description (string) ├── module\_paths ([][]str... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/import-reference/tfconfig.mdx | main | terraform | [
-0.03724582865834236,
0.06801741570234299,
-0.0037875273264944553,
0.008692199364304543,
0.022823186591267586,
-0.0028043778147548437,
0.04597160965204239,
-0.001692384947091341,
-0.0032971655018627644,
0.02303023263812065,
0.03345199674367905,
-0.09298020601272583,
0.10694249719381332,
-0... | 0.010825 |
main = rule { subject.module(["foo"]).resources.null\_resource.foo.config.triggers[0].foo is "bar" } ``` ### Value: `module\_paths` \* \*\*Value Type:\*\* List of a list of strings. The `module\_paths` value within the [root namespace](#namespace-root) is a list of all of the modules within the Terraform configuration.... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/import-reference/tfconfig.mdx | main | terraform | [
-0.03719453886151314,
0.04247044026851654,
0.035069722682237625,
0.026302680373191833,
0.061476729810237885,
-0.06519405543804169,
0.038429148495197296,
-0.047721873968839645,
0.01969507709145546,
0.014742914587259293,
0.021722886711359024,
-0.052058737725019455,
0.0779787078499794,
-0.027... | 0.028069 |
data sources, use the same syntax, except with `data` in place of `resources`. ### Value: `config` \* \*\*Value Type:\*\* A string-keyed map of values. The `config` value within the [resource namespace](#namespace-resources-data-sources) is a map of key-value pairs that directly map to Terraform config keys and values.... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/import-reference/tfconfig.mdx | main | terraform | [
-0.05763954669237137,
0.06357241421937943,
-0.006939605809748173,
0.027385588735342026,
-0.005842703394591808,
-0.02335551753640175,
0.08406446874141693,
-0.03662044182419777,
-0.012305022217333317,
0.025762634351849556,
-0.0019502838840708137,
-0.10346728563308716,
0.1189611628651619,
-0.... | 0.039948 |
tfconfig.resources.null\_resource.foo.provisioners[0].type is "local-exec" } ``` ## Namespace: Module Configuration The \*\*module configuration\*\* namespace displays data on \_module configuration\_ as it is given within a `module` block. This means that the namespace concerns itself with the contents of the declarat... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/import-reference/tfconfig.mdx | main | terraform | [
-0.04061690345406532,
0.005220895167440176,
-0.08025066554546356,
0.07156158238649368,
0.00503462553024292,
-0.03213485702872276,
0.07971451431512833,
0.04517602548003197,
-0.005073751322925091,
-0.0699511170387268,
0.04651844501495361,
-0.08792562782764435,
0.043026357889175415,
0.0043485... | -0.011714 |
within the [output namespace](#namespace-outputs) represents the defined description for this output. As an example, given the following output declaration block: ```hcl output "id" { description = "foobar" value = "${null\_resource.foo.id}" } ``` The following policy would evaluate to `true`: ```python import "tfconfi... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/import-reference/tfconfig.mdx | main | terraform | [
-0.040043629705905914,
0.05796709284186363,
-0.05222969874739647,
0.052530061453580856,
0.03586456924676895,
-0.013364746235311031,
0.0694895014166832,
-0.006750090047717094,
0.04489085450768471,
-0.06024978682398796,
-0.021168241277337074,
-0.10921646654605865,
0.10501951724290848,
0.0301... | 0.09025 |
tfconfig.providers.aws.alias.east.config.region is "us-east-1" } ``` ### Value: `config` \* \*\*Value Type:\*\* A string-keyed map of values. -> \*\*With Terraform 0.11 or earlier\*\*, if the config value is defined as an expression (and not a static value), the value will be in its raw, non-interpolated string. \*\*Wi... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/import-reference/tfconfig.mdx | main | terraform | [
-0.003785186680033803,
0.04755531623959541,
0.062043558806180954,
-0.01721118576824665,
0.0086493119597435,
-0.023880772292613983,
0.051422350108623505,
-0.02899443916976452,
0.007498595397919416,
0.04444010928273201,
0.01727701909840107,
-0.1001087948679924,
0.03397601842880249,
-0.031577... | -0.036938 |
# tfplan Sentinel import reference ~> \*\*Warning:\*\* The `tfplan` import is now deprecated and will be permanently removed in August 2025. We recommend that you start using the updated [tfplan/v2](/terraform/cloud-docs/policy-enforcement/import-reference/tfplan-v2) import as soon as possible to avoid disruptions. The... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/import-reference/tfplan.mdx | main | terraform | [
-0.06409687548875809,
0.013351762667298317,
0.051797594875097275,
0.0035025053657591343,
0.11129549890756607,
-0.055799830704927444,
-0.011994271539151669,
-0.02888433448970318,
-0.006167371291667223,
0.10345572233200073,
-0.002045739209279418,
-0.019316652789711952,
-0.017609981819987297,
... | 0.100218 |
``` module = func(ADDR) ``` \* \*\*Return Type:\*\* A [module namespace](#namespace-module). The `module()` function in the [root namespace](#namespace-root) returns the [module namespace](#namespace-module) for a particular module address. The address must be a list and is the module address, split on the period (`.`)... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/import-reference/tfplan.mdx | main | terraform | [
-0.0835341364145279,
-0.05687649920582771,
-0.03738628327846527,
0.06254146993160248,
0.005387785378843546,
-0.04808364808559418,
0.029561465606093407,
0.007390697952359915,
0.01699981652200222,
-0.07212518155574799,
0.04742474853992462,
-0.016232077032327652,
0.01907929964363575,
0.026739... | 0.143482 |
/terraform/cloud-docs/policy-enforcement/import-reference/tfconfig-v2#value-default [import-tfconfig-variables]: /terraform/cloud-docs/policy-enforcement/import-reference/tfconfig-v2#namespace-variables If a default was accepted for the particular variable, the default value will be populated here. As an example, given... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/import-reference/tfplan.mdx | main | terraform | [
0.001114736427552998,
0.05641666054725647,
0.03303912654519081,
0.006159094162285328,
-0.0115357656031847,
0.0027601136825978756,
0.042823273688554764,
-0.05449410900473595,
0.003804614534601569,
0.05120697617530823,
0.02212405577301979,
-0.08628201484680176,
0.03183482214808464,
0.0138662... | -0.02844 |
fetch all resources within the root module, irrespective of type, use `tfplan.resources`. This is indexed by type, as shown above with `tfplan.resources.aws\_instance`, with names being the next level down, and so on. ~> When [resource targeting](/terraform/cli/commands/plan#resource-targeting) is in effect, `tfplan.re... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/import-reference/tfplan.mdx | main | terraform | [
-0.030149834230542183,
0.032075848430395126,
0.023432569578289986,
0.00382906012237072,
0.09000377357006073,
-0.08278246223926544,
0.06570945680141449,
-0.0580616295337677,
0.07043115049600601,
0.060721371322870255,
0.005476485006511211,
-0.07478755712509155,
0.04581541568040848,
-0.023191... | 0.004083 |
resource: ```hcl resource "null\_resource" "foo" { triggers = { foo = "bar" } } ``` The following policy would evaluate to `true` if one of the `triggers` in `null\_resource.foo` was being changed: ```python import "tfplan" main = rule { tfplan.resources.null\_resource.foo[0].requires\_new } ``` ## Namespace: Resource ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/import-reference/tfplan.mdx | main | terraform | [
-0.09685356169939041,
0.03681252524256706,
0.008274381048977375,
0.03493422269821167,
0.06570509821176529,
-0.10693689435720444,
0.11272959411144257,
-0.0725889652967453,
0.052446264773607254,
-0.0004446349339559674,
0.06401326507329941,
-0.07375504076480865,
0.08349518477916718,
-0.027561... | 0.044744 |
{ triggers = { foo = "bar" } } ``` The following policy would evaluate to `true`: ```python import "tfplan" main = rule { tfplan.resources.null\_resource.foo[0].diff["triggers.foo"].old is "bar" } ``` | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/import-reference/tfplan.mdx | main | terraform | [
-0.045421600341796875,
0.0805487260222435,
0.016872094944119453,
0.007234819233417511,
0.08241897821426392,
-0.09327884763479233,
0.11169552803039551,
-0.019766421988606453,
0.022047415375709534,
0.006707062944769859,
0.06361651420593262,
-0.01728850044310093,
0.05224180594086647,
-0.00552... | 0.031868 |
# `import` function reference overview This topic provides an overview of the Sentinel `import` function, which you can use to import Sentinel libraries into your custom Sentinel policies. Refer to [Define custom Sentinel policies](/terraform/cloud-docs/policy-enforcement/define-policies/custom-sentinel) for additional... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/import-reference/index.mdx | main | terraform | [
-0.019908303394913673,
-0.0028841490857303143,
0.007713188882917166,
-0.03649124875664711,
0.06305419653654099,
0.014782475307583809,
0.0037118084728717804,
-0.026531072333455086,
-0.039265263825654984,
0.05255556479096413,
-0.004310637712478638,
-0.03926292434334755,
0.029786445200443268,
... | 0.101026 |
-> \*\*Note:\*\* This is documentation for the next version of the `tfconfig` Sentinel import, designed specifically for Terraform 0.12. This import requires Terraform 0.12 or higher, and must currently be loaded by path, using an alias, example: `import "tfconfig/v2" as tfconfig`. # tfconfig/v2 Sentinel import The `tf... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/import-reference/tfconfig-v2.mdx | main | terraform | [
-0.022201385349035263,
-0.02068931981921196,
-0.01295444369316101,
-0.032103534787893295,
0.010452162474393845,
-0.02329627238214016,
0.016292601823806763,
-0.013374322094023228,
0.025568349286913872,
0.0375109426677227,
-0.009377783164381981,
-0.05118722468614578,
-0.010941706597805023,
-... | 0.136529 |
all output definitions across all modules in the configuration. \* [`module\_calls`](#the-module\_calls-collection) - The configuration of all module calls (individual [`module`](/terraform/language/modules) blocks) across all modules in the configuration. These collections are specifically designed to be used with the... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/import-reference/tfconfig-v2.mdx | main | terraform | [
-0.02836833894252777,
0.01717471331357956,
-0.028058597818017006,
0.059979017823934555,
0.08404397964477539,
-0.015228988602757454,
0.05993224307894707,
-0.06638014316558838,
0.030406109988689423,
-0.02357112057507038,
-0.02964700572192669,
-0.07096078246831894,
0.013015640899538994,
0.019... | 0.079666 |
`references` field. More details on this field can be found in the [expression representation](/terraform/internals/json-format#expression-representation) section of the JSON output format documentation. For example, to determine if an output is based on a particular resource value, one could do: ``` import "tfconfig/v... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/import-reference/tfconfig-v2.mdx | main | terraform | [
-0.09554888308048248,
0.07704740017652512,
0.005110662896186113,
0.03531361743807793,
0.06974311172962189,
-0.008413729257881641,
0.02950320765376091,
-0.021065784618258476,
0.0894264504313469,
-0.012073584832251072,
-0.04268697276711464,
-0.07797187566757202,
0.024541031569242477,
0.01253... | 0.072673 |
a list indexed by the order the provisioners show up in the resource. \* `config` - The [block expression representation](#block-expression-representation) of the configuration values found in the resource. \* `count` - The [expression data](#expression-representations) for the `count` value in the resource. \* `for\_e... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/import-reference/tfconfig-v2.mdx | main | terraform | [
-0.062101561576128006,
0.04839523509144783,
0.001620491617359221,
0.06675222516059875,
0.08678627014160156,
-0.01311059482395649,
0.08463161438703537,
-0.07069575786590576,
0.03886392340064049,
-0.011342168785631657,
0.00997111201286316,
-0.0054817721247673035,
0.051000695675611496,
-0.007... | 0.08467 |
indexed by the key format `module\_address:name`, with each field matching their respective name below. `module\_address` and the colon delimiter are omitted for the root module. \* `module\_address` - The address of the module the declaration was found in. \* `name` - The name of the module. \* `source` - The contents... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/import-reference/tfconfig-v2.mdx | main | terraform | [
-0.014952786266803741,
0.01160228531807661,
-0.04759687930345535,
0.06183525174856186,
-0.0009574988507665694,
0.01727943681180477,
0.06272298842668533,
-0.007273306138813496,
0.01559393759816885,
-0.07141625136137009,
-0.010289841331541538,
-0.02433437667787075,
0.06284923851490021,
-0.06... | 0.105789 |
-> \*\*Note:\*\* This is documentation for the next version of the `tfplan` Sentinel import, designed specifically for Terraform 0.12. This import requires Terraform 0.12 or higher, and must currently be loaded by path, using an alias, example: `import "tfplan/v2" as tfplan`. # tfplan/v2 Sentinel import The `tfplan/v2`... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/import-reference/tfplan-v2.mdx | main | terraform | [
-0.05394239351153374,
0.04310164973139763,
0.044737424701452255,
-0.024787645787000656,
0.03549912944436073,
-0.07212135195732117,
0.010386945679783821,
-0.018259476870298386,
0.03382107987999916,
0.08057025820016861,
0.0005765420501120389,
-0.047507524490356445,
-0.014790565706789494,
-0.... | 0.111205 |
having to write complex discovery code. As an example, the following code will return all `aws\_instance` resource changes, across all modules in the plan: ``` all\_aws\_instances = filter tfplan.resource\_changes as \_, rc { rc.mode is "managed" and rc.type is "aws\_instance" } ``` You can add specific attributes to t... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/import-reference/tfplan-v2.mdx | main | terraform | [
-0.052092768251895905,
0.08542500436306,
-0.021616963669657707,
0.054608579725027084,
0.09180734306573868,
-0.019340800121426582,
0.08985361456871033,
-0.07106125354766846,
0.03368840366601944,
-0.011767405085265636,
0.00013926016981713474,
-0.07078837603330612,
0.049088310450315475,
0.008... | 0.038971 |
- Applies to default lifecycle configurations. \* \*\*Create-before-destroy:\*\* `["create", "delete"]` - Applies when [`create\_before\_destroy`](/terraform/language/meta-arguments/lifecycle#create\_before\_destroy) is used in a lifecycle configuration. Note that, in most situations, the plan will list all "changes", ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/import-reference/tfplan-v2.mdx | main | terraform | [
-0.051121462136507034,
0.08688022196292877,
0.045557960867881775,
-0.01097483653575182,
0.09553036838769913,
-0.05630125850439072,
0.08252564072608948,
-0.08909790217876434,
0.060810305178165436,
0.05000657960772514,
-0.009907620027661324,
-0.0577496737241745,
0.003558229887858033,
0.02366... | 0.014892 |
the collection key. \* `value` - The value of the variable assigned during the plan. ## The `planned\_values` Collection The `planned\_values` collection is a special collection in that it contains two fields that alias to state collections with the \_planned\_ state set. This is the best prediction of what the state w... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/import-reference/tfplan-v2.mdx | main | terraform | [
-0.05057692900300026,
0.06916394829750061,
-0.024026699364185333,
0.0008602701709605753,
0.02071167342364788,
-0.005549078807234764,
0.025371968746185303,
-0.06385510414838791,
0.06998927891254425,
0.05184057727456093,
-0.006327833514660597,
-0.06209465116262436,
0.06089325249195099,
-0.05... | 0.090259 |
value are below: \* `name` - The name of the output, also the index key. \* `change` - The data describing the change that will be made to this output. For more details, see [Change Representation](#change-representation). ## The `raw` Collection The `raw` collection exposes the raw, unprocessed plan data, direct from ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/import-reference/tfplan-v2.mdx | main | terraform | [
-0.04709022864699364,
0.1126607209444046,
0.007079934701323509,
-0.03387277573347092,
0.0003248772118240595,
0.0040377406403422356,
-0.03954034298658371,
-0.06217649206519127,
-0.004732224624603987,
0.022422460839152336,
0.019566088914871216,
-0.07495642453432083,
0.04301362484693527,
-0.0... | 0.021836 |
# Import: tfstate ~> \*\*Warning:\*\* The `tfstate` import is now deprecated and will be permanently removed in August 2025. We recommend that you start using the updated [tfstate/v2](/terraform/cloud-docs/policy-enforcement/import-reference/tfstate-v2) import as soon as possible to avoid disruptions. The `tfstate/v2` ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/import-reference/tfstate.mdx | main | terraform | [
-0.025954974815249443,
0.010516108945012093,
0.034797269850969315,
-0.04610768333077431,
0.06678874045610428,
0.004703056998550892,
0.03694656863808632,
-0.06360868364572525,
-0.00002798072455334477,
0.06910569220781326,
-0.032324548810720444,
-0.06741432845592499,
0.03264797478914261,
-0.... | 0.073588 |
triggers = { foo = "bar" } } ``` The following policy would evaluate to `true` if the resource was present in the state: ```python import "tfstate" main = rule { tfstate.module(["foo"]).resources.null\_resource.foo[0].attr.triggers.foo is "bar" } ``` ### Value: `module\_paths` \* \*\*Value Type:\*\* List of a list of s... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/import-reference/tfstate.mdx | main | terraform | [
-0.033358387649059296,
0.01960417442023754,
0.06420700997114182,
0.03153739124536514,
0.08174040913581848,
-0.058276984840631485,
0.06738080084323883,
-0.061828941106796265,
0.04538555070757866,
0.03763439133763313,
0.017638031393289566,
-0.05828295275568962,
0.08997729420661926,
-0.011919... | 0.070282 |
`path` value within the [module namespace](#namespace-module) contains the path of the module that the namespace represents. This is represented as a list of strings. As an example, if the following module block was present within a Terraform configuration: ```hcl module "foo" { # ... } ``` The following policy would e... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/import-reference/tfstate.mdx | main | terraform | [
-0.05502140149474144,
0.0243468526750803,
-0.005822137929499149,
0.033554740250110626,
0.035532910376787186,
-0.04482104629278183,
0.08626363426446915,
-0.05178019031882286,
0.046871840953826904,
-0.003278611460700631,
-0.020837103947997093,
-0.08112768828868866,
0.08579820394515991,
0.019... | 0.057605 |
= "bar" } } resource "null\_resource" "bar" { # ... depends\_on = [ "null\_resource.foo", ] } ``` The following policy would evaluate to `true` if the resource was in the state: ```python import "tfstate" main = rule { tfstate.resources.null\_resource.bar[0].depends\_on contains "null\_resource.foo" } ``` ### Value: `i... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/import-reference/tfstate.mdx | main | terraform | [
-0.08534706383943558,
0.05107903108000755,
0.0020595965906977654,
0.03421308472752571,
0.0217521283775568,
-0.030452268198132515,
0.11742690205574036,
-0.04496360942721367,
0.007106519304215908,
0.005658650770783424,
-0.015850631520152092,
-0.0908735990524292,
0.08137353509664536,
0.014739... | 0.035953 |
question. Note that the only valid primitive output type in Terraform is currently a string, which means that any int, float, or boolean value will need to be converted before it can be used in comparison. This does not apply to primitives within maps and lists, which will be their original types. As an example, given ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/import-reference/tfstate.mdx | main | terraform | [
0.030025547370314598,
0.09884725511074066,
0.05282570794224739,
-0.013828014954924583,
0.012539158575236797,
-0.012011914514005184,
0.03809187561273575,
-0.04913131892681122,
-0.04073571786284447,
0.040057867765426636,
-0.0525004044175148,
-0.07284688949584961,
0.03933482617139816,
0.03683... | 0.001795 |
# Define Sentinel policies in HCP Terraform This topic describes how to create and manage custom policies using Sentinel policy language. For instructions about how to use pre-written Sentinel policies from the registry, refer to [Run pre-written Sentinel policies](/terraform/cloud-docs/policy-enforcement/prewritten-se... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/define-policies/custom-sentinel.mdx | main | terraform | [
-0.01175743993371725,
-0.0018396046943962574,
0.009777112863957882,
-0.02918793447315693,
0.019625086337327957,
0.02346244640648365,
0.03257221728563309,
-0.013192393817007542,
-0.03144446015357971,
0.06781642884016037,
-0.03454133868217468,
-0.05202079564332962,
0.042177725583314896,
-0.0... | 0.094111 |
example function does several useful things while finding resources: - It checks every module (including the root module) for resources of the specified type by iterating over the `module\_paths` namespace. The top-level `resources` namespace is more convenient, but it only reveals resources from the root module. - It ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/define-policies/custom-sentinel.mdx | main | terraform | [
-0.038305237889289856,
0.009637638926506042,
0.017240585759282112,
0.061060961335897446,
0.10568807274103165,
-0.06434077769517899,
0.032690323889255524,
-0.04165464639663696,
0.03105958364903927,
0.017063291743397713,
-0.025554321706295013,
-0.030995098873972893,
0.007536532357335091,
0.0... | 0.198271 |
condition in this case since the applied value will not be known. While this function allows a rule to validate an attribute against a list, some rules will only need to validate an attribute against a single value; in those cases, you could either use a list with a single value or embed that value inside the function ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/define-policies/custom-sentinel.mdx | main | terraform | [
-0.01951713114976883,
0.07363714277744293,
0.03276318311691284,
0.0291381124407053,
0.08129415661096573,
-0.04872016981244087,
0.04684846103191376,
0.007942628115415573,
-0.07465439289808273,
-0.05401398614048958,
-0.038367584347724915,
-0.061663128435611725,
0.05526767671108246,
0.0792669... | 0.017452 |
# Define policies overview This topic provides overview information about how to define policies as code. Policies are rules for enforcing how Terraform provisions infrastructure as code for your workspaces and projects. ## Workflows You can use two policy-as-code frameworks to define fine-grained, logic-based policies... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/define-policies/index.mdx | main | terraform | [
-0.03723403438925743,
0.01749821938574314,
0.026996079832315445,
-0.0023833352606743574,
0.019651029258966446,
-0.05538618192076683,
-0.00474339397624135,
-0.04923514276742935,
-0.014987451955676079,
0.10599169135093689,
-0.049891382455825806,
-0.0352533720433712,
0.012404512614011765,
0.0... | 0.103447 |
# Define Open Policy Agent policies for HCP Terraform This topic describes how to create and manage custom policies using the open policy agent (OPA) framework. Refer to the following topics for instructions on using HashiCorp Sentinel policies: - [Define custom Sentinel policies](/terraform/cloud-docs/policy-enforceme... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/define-policies/opa.mdx | main | terraform | [
-0.021769443526864052,
0.038208574056625366,
0.05248064547777176,
-0.03711549565196037,
-0.007468828000128269,
-0.05995792895555496,
0.023004913702607155,
-0.011045261286199093,
-0.03226390853524208,
0.09780768305063248,
-0.01487121544778347,
-0.05648770555853844,
0.036523908376693726,
-0.... | 0.109724 |
msg := sprintf( "HCP Terraform workspace %s has been configured to automatically provision Terraform infrastructure. Change the workspace Apply Method settings to 'Manual Apply'", [run.workspace.name], ) } ``` The following test validates `block\_auto\_apply\_runs`. The test is written in rego and uses the OPA [test fo... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/define-policies/opa.mdx | main | terraform | [
-0.0314369797706604,
0.008281601592898369,
0.019204355776309967,
-0.002223346149548888,
0.0042644161731004715,
-0.06992821395397186,
-0.03548358380794525,
-0.018318675458431244,
-0.01431233435869217,
0.09488648921251297,
0.004992095287889242,
-0.09132932871580124,
0.006792341358959675,
0.0... | 0.020279 |
property is a boolean, indicating whether the variable is a [sensitive value](/terraform/cloud-docs/variables/managing-variables#sensitive-values). | #### Project Namespace The following table contains the properties for the `project` namespace. | Property Name | Type | Description | |---------- | ------------ | ------... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/policy-enforcement/define-policies/opa.mdx | main | terraform | [
-0.0031168016139417887,
0.02705984376370907,
-0.005960042588412762,
0.05822720006108284,
-0.06420902907848358,
-0.007881661877036095,
0.05896187201142311,
-0.07057633250951767,
0.011496873572468758,
0.047144487500190735,
-0.01993955858051777,
-0.13719874620437622,
0.09478937834501266,
-0.0... | 0.042119 |
[private]: /terraform/cloud-docs/registry [speculative plan]: /terraform/cloud-docs/workspaces/run/remote-operations#speculative-plans [tfe-provider]: https://registry.terraform.io/providers/hashicorp/tfe/latest/docs # The CLI-driven remote run workflow > \*\*Hands-on:\*\* Try the [Log in to HCP Terraform from the CLI]... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/run/cli.mdx | main | terraform | [
0.006843152921646833,
0.02304481714963913,
0.00923018530011177,
-0.06099811568856239,
-0.05060475692152977,
-0.05503048375248909,
-0.0684325248003006,
-0.04181019961833954,
0.019152343273162842,
0.053740035742521286,
-0.06047120317816734,
-0.08168606460094452,
0.04192504286766052,
-0.00820... | 0.07865 |
{ organization = "my-org" workspaces { tags = ["networking"] } } } ``` -> \*\*Note:\*\* The `cloud` block is available in Terraform v1.1 and later. Previous versions can use the [`remote` backend](/terraform/language/settings/backends/remote) to configure the CLI workflow and migrate state. 1. Run `terraform init`. ```... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/run/cli.mdx | main | terraform | [
-0.01631852239370346,
-0.0502442792057991,
0.05815042927861214,
-0.04984477162361145,
0.00338270072825253,
-0.034816160798072815,
-0.04321931675076485,
-0.11634007841348648,
-0.020878806710243225,
0.03724392130970955,
0.011775882914662361,
-0.06664030998945236,
0.016977844759821892,
-0.001... | 0.021909 |
-> \*\*Version note:\*\* `.terraformignore` support was added in Terraform 0.12.11. CLI-driven runs upload an archive of your configuration directory to HCP Terraform. If the directory contains files you want to exclude from upload, you can do so by defining a [`.terraformignore` file in your configuration directory](/... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/run/cli.mdx | main | terraform | [
0.006968043744564056,
0.07622607797384262,
0.0034983642399311066,
-0.0007767052738927305,
0.004085786174982786,
-0.04714100435376167,
-0.0042081004939973354,
-0.07424517720937729,
0.012232520617544651,
0.03224698081612587,
-0.02458438090980053,
-0.05163881182670593,
0.053925395011901855,
-... | 0.00395 |
run `terraform apply -auto-approve` with the saved plan. - \*\*Remote Execution:\*\* HCP Terraform does not support uploading saved plans for remote execution, so we recommend running `terraform apply -auto-approve` immediately after approving the speculative plan to prevent the plan from becoming stale. !> \*\*Warning... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/run/cli.mdx | main | terraform | [
-0.025779936462640762,
0.04778052493929863,
0.0850013718008995,
-0.033010903745889664,
0.019601695239543915,
-0.037463508546352386,
-0.07208839058876038,
-0.07131549715995789,
-0.007094904780387878,
0.10232435166835785,
-0.03672488033771515,
-0.06756589561700821,
0.018176674842834473,
-0.0... | -0.011579 |
terraform apply [...] Plan: 1 to add, 0 to change, 1 to destroy. ------------------------------------------------------------------------ Organization policy check: Sentinel Result: false Sentinel evaluated to false because one or more Sentinel policies evaluated to false. This false was not due to an undefined value o... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/run/cli.mdx | main | terraform | [
-0.012100991792976856,
0.008677566424012184,
0.07996132224798203,
0.02041669376194477,
0.05257304757833481,
-0.05682120472192764,
-0.0025855661369860172,
-0.057367030531167984,
-0.003327737096697092,
0.12485141307115555,
-0.013136018067598343,
-0.047316811978816986,
0.004605788737535477,
0... | 0.015363 |
# HCP Terraform's run environment HCP Terraform is designed as an execution platform for Terraform, and most of its features are based around its ability to perform Terraform runs in a fleet of disposable worker VMs. This page describes some features of the run environment for Terraform runs managed by HCP Terraform. #... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/run/run-environment.mdx | main | terraform | [
0.031664200127124786,
0.034255798906087875,
0.03536604717373848,
-0.0189621951431036,
-0.011586309410631657,
-0.04232972115278244,
-0.081743523478508,
-0.06781087070703506,
-0.02210419625043869,
0.037393968552351,
-0.04695853218436241,
-0.0405987873673439,
0.005765355192124844,
-0.04737512... | 0.110405 |
Previous versions can use the [`remote` backend](/terraform/language/settings/backends/remote) to configure the CLI workflow and migrate state. ### Autogenerated API Token Instead of using existing user credentials, HCP Terraform generates a unique per-run API token and provides it to the Terraform worker in the [CLI c... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/run/run-environment.mdx | main | terraform | [
-0.03295611962676048,
-0.02449401281774044,
0.003346903482452035,
-0.05369812995195389,
-0.041745491325855255,
0.005954259540885687,
-0.028064018115401268,
-0.0448574498295784,
0.011891704052686691,
0.02296445518732071,
-0.07249952852725983,
-0.06588618457317352,
0.048081863671541214,
0.02... | 0.059167 |
| The name of the branch that the associated Terraform configuration version was ingressed from. | `main` | | `TFC\_CONFIGURATION\_VERSION\_GIT\_COMMIT\_SHA` | The full commit hash of the commit that the associated Terraform configuration version was ingressed from. | `abcd1234...` | | `TFC\_CONFIGURATION\_VERSION\_GIT... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/run/run-environment.mdx | main | terraform | [
0.018017971888184547,
0.03113352134823799,
-0.008480967953801155,
-0.021396655589342117,
0.016563288867473602,
0.007610526867210865,
0.005989175755530596,
-0.013531124219298363,
0.05008010193705559,
0.05697305500507355,
0.010335986502468586,
-0.03712739795446396,
0.04420219734311104,
-0.05... | 0.050098 |
# Run states and stages Each plan and apply run passes through several stages of action: pending, plan, cost estimation, policy check, apply, and completion. HCP Terraform shows a run's progress through each stage as a run state. In the list of workspaces on HCP Terraform's main page, each workspace shows the state of ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/run/states.mdx | main | terraform | [
-0.005277056712657213,
0.03621301054954529,
0.06790453940629959,
-0.0027016308158636093,
0.008586659096181393,
-0.016931898891925812,
0.0011096770176663995,
-0.1071915253996849,
0.00726680364459753,
0.04509966820478439,
-0.040115274488925934,
-0.067698173224926,
0.04295223206281662,
-0.052... | 0.073179 |
in this stage:\_ - \*\*Planning:\*\* HCP Terraform is currently running `terraform plan`. - \*\*Needs Confirmation:\*\* `terraform plan` has finished. Runs sometimes pause in this state, depending on the workspace and organization settings. \_Leaving this stage:\_ - If the `terraform plan` command failed, the run does ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/run/states.mdx | main | terraform | [
-0.0028990551363676786,
0.05298550799489021,
0.06551044434309006,
0.021057171747088432,
0.03366817533969879,
-0.006691907066851854,
-0.007905859500169754,
-0.0759214237332344,
0.016351159662008286,
0.07680163532495499,
-0.025557152926921844,
-0.07131443917751312,
0.035040728747844696,
-0.0... | 0.104861 |
you enabled [Open Policy Agent (OPA) policies](/terraform/cloud-docs/policy-enforcement/opa) and runs after a successful `terraform plan` and before Cost Estimation. In this stage, HCP Terraform checks whether the plan adheres to the policies in the OPA policy sets for the workspace. \_States in this stage:\_ - \*\*Pol... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/run/states.mdx | main | terraform | [
0.0022471954580396414,
0.014749038964509964,
0.06111958622932434,
0.024434693157672882,
0.003990514203906059,
-0.06355109810829163,
-0.025387510657310486,
-0.06231851875782013,
0.003778328187763691,
0.09724341332912445,
-0.023449430242180824,
-0.060078538954257965,
0.014544888399541378,
-0... | -0.016178 |
If a user with permission to manage policy overrides, overrides the failed policy, the run proceeds to the \*\*Policy Checked\*\* state. ([More about permissions.](/terraform/cloud-docs/users-teams-organizations/permissions)) - If a user with permission to apply runs discards the run, the run does not continue (\*\*Dis... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/run/states.mdx | main | terraform | [
-0.023692462593317032,
0.043159473687410355,
0.06508004665374756,
-0.0024171415716409683,
0.011622722260653973,
-0.053590819239616394,
-0.00006555314030265436,
-0.06579510867595673,
-0.005529513116925955,
0.11480268090963364,
-0.02730793133378029,
0.022880014032125473,
0.00919268187135458,
... | 0.018571 |
from the configured external system(s). - External systems must respond initially with a `200 OK` acknowledging the request is in progress. After that, they have 10 minutes to return a status of `passed`, `running`, or `failed`. If the timeout expires, HCP Terraform assumes that the run tasks is in the `failed` status.... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/run/states.mdx | main | terraform | [
-0.043538469821214676,
0.05107695981860161,
0.04195595532655716,
0.009078503586351871,
0.0175715833902359,
-0.03781610354781151,
-0.027943605557084084,
-0.0515066497027874,
0.01622762344777584,
0.05275312811136246,
-0.029887663200497627,
-0.059576258063316345,
0.059354763478040695,
-0.0555... | 0.08982 |
# Remote operations > \*\*Hands-on:\*\* Try the [Get Started — HCP Terraform](/terraform/tutorials/cloud-get-started?utm\_source=WEBSITE&utm\_medium=WEB\_IO&utm\_offer=ARTICLE\_PAGE&utm\_content=DOCS) tutorials. HCP Terraform provides a central interface for running Terraform within a large collaborative organization. ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/run/remote-operations.mdx | main | terraform | [
0.004209311679005623,
0.005443086847662926,
0.003823960432782769,
-0.01853053830564022,
-0.035567473620176315,
-0.037466343492269516,
-0.0675484836101532,
-0.0348832942545414,
-0.01389964111149311,
0.0644654706120491,
-0.01851613260805607,
-0.052933309227228165,
0.05578926205635071,
-0.066... | 0.105021 |
Runs that are waiting for other runs to finish are in a \_pending\_ state, and a workspace might have any number of pending runs. There are two exceptions to the run queue, which can proceed at any time and do not block the progress of other runs: - Plan-only runs. - The planning stages of [saved plan runs](/terraform/... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/run/remote-operations.mdx | main | terraform | [
-0.005190461408346891,
-0.00916933175176382,
0.04533927142620087,
0.010508207604289055,
-0.015991317108273506,
-0.0035948692820966244,
-0.05732876807451248,
-0.1359037607908249,
0.0647580549120903,
0.0750693827867508,
-0.04202931374311447,
-0.006209094077348709,
-0.009565627202391624,
-0.0... | 0.027864 |
because they don't affect real infrastructure. HCP Terraform lists past speculative plan runs alongside a workspace's other runs. There are three ways to run speculative plans: - In VCS-backed workspaces, pull requests start speculative plans, and the VCS provider's pull request interface includes a link to the plan. S... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/run/remote-operations.mdx | main | terraform | [
-0.005117230117321014,
-0.002858510008081794,
0.07849868386983871,
0.001145809656009078,
0.04945074021816254,
-0.06206030398607254,
-0.05059477686882019,
-0.058084167540073395,
0.09613615274429321,
0.03886224702000618,
-0.06251341104507446,
-0.026260647922754288,
0.006046098656952381,
-0.0... | -0.000706 |
# Install software in the run environment Terraform relies on provider plugins to manage resources. In most cases, Terraform can automatically download the required plugins, but there are cases where plugins must be managed explicitly. In rare cases, it might also be necessary to install extra software on the Terraform... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/run/install-software.mdx | main | terraform | [
0.009962871670722961,
-0.05981398746371269,
0.019637061282992363,
-0.023678112775087357,
-0.022389136254787445,
-0.04321237653493881,
-0.0333702452480793,
-0.044985875487327576,
0.01655876822769642,
0.05216743424534798,
0.015801768749952316,
-0.03639944642782211,
-0.014070011675357819,
0.0... | 0.080888 |
to a configuration repo, or you can add them as Git submodules and symlink the executable files into `terraform.d/plugins/`. Submodules are a good choice when many workspaces use the same custom provider, since they keep your repos smaller. If using submodules, enable the ["Include submodules on clone" setting](/terraf... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/run/install-software.mdx | main | terraform | [
-0.04657858610153198,
-0.08485904335975647,
0.06855680048465729,
0.015866095200181007,
-0.020725419744849205,
-0.012000559829175472,
-0.013962149620056152,
-0.04266991466283798,
-0.0012086306232959032,
0.10191009193658829,
0.00005452343248180114,
-0.040563806891441345,
0.02122853882610798,
... | 0.028528 |
# UI and VCS-driven run workflow HCP Terraform has three workflows for managing Terraform runs. - The UI/VCS-driven run workflow described below, which is the primary mode of operation. - The [API-driven run workflow](/terraform/cloud-docs/workspaces/run/api), which is more flexible but requires you to create some tool... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/run/ui.mdx | main | terraform | [
-0.05234444886445999,
0.007980040274560452,
0.00004199211616651155,
-0.023405417799949646,
-0.012978754937648773,
-0.0553162656724453,
-0.054111432284116745,
-0.06236414611339569,
0.06780635565519333,
0.04352429509162903,
-0.06915678828954697,
-0.075107641518116,
0.02472730167210102,
-0.03... | 0.137683 |
supported options. Run modes that have a plan phase support debugging mode. This is equivalent to setting the `TF\_LOG` environment variable to `TRACE` for this run only. To enable debugging, click \*\*Additional planning options\*\* under the run mode and click \*\*Enable debugging mode\*\*. See [Debugging Terraform](... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/run/ui.mdx | main | terraform | [
0.00500753428786993,
0.029742654412984848,
0.06651579588651657,
0.06513266265392303,
0.058983348309993744,
-0.08671413362026215,
-0.03469128534197807,
-0.11073978990316391,
0.021599918603897095,
0.11899527907371521,
-0.05428994446992874,
-0.035366132855415344,
-0.01576392538845539,
0.02321... | -0.007663 |
executing malicious code or exposing sensitive information, HCP Terraform doesn't run speculative plans for pull requests that originate from forks of a repository. -> \*\*Note:\*\* On Terraform Enterprise, administrators can choose to allow speculative plans on pull requests that originate from forks. To learn more ab... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/run/ui.mdx | main | terraform | [
-0.02232043817639351,
0.028750069439411163,
0.07271569222211838,
-0.02022801712155342,
-0.023041104897856712,
-0.03500301018357277,
0.0016007001977413893,
-0.051944512873888016,
0.04296331852674484,
0.08294220268726349,
-0.04059009253978729,
-0.059758611023426056,
0.00451116356998682,
-0.0... | 0.00578 |
# The API-driven run workflow HCP Terraform has three workflows for managing Terraform runs. - The [UI/VCS-driven run workflow](/terraform/cloud-docs/workspaces/run/ui), which is the primary mode of operation. - The API-driven run workflow described below, which is more flexible but requires you to create some tooling.... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/run/api.mdx | main | terraform | [
-0.059647176414728165,
0.009589887224137783,
0.015044262632727623,
-0.012914229184389114,
-0.02586883306503296,
-0.06507834047079086,
-0.08165481686592102,
-0.07520187646150589,
0.058338191360235214,
0.024187423288822174,
-0.06769493222236633,
-0.0934956818819046,
0.02712130919098854,
-0.0... | 0.090974 |
Workspace ID The first step identified the organization name and the workspace name; however, the [configuration version API](/terraform/cloud-docs/api-docs/configuration-versions) expects the workspace ID. As such, the ID has to be looked up. If the workspace ID is already known, this step can be skipped. This step us... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/run/api.mdx | main | terraform | [
-0.0514521449804306,
0.05680328607559204,
-0.0016538426280021667,
0.03728650510311127,
-0.007177263963967562,
-0.025600122287869453,
-0.0278445016592741,
-0.06479642540216446,
0.06301391869783401,
0.07985293120145798,
-0.02365681156516075,
-0.06071856617927551,
0.04340564087033272,
0.00617... | 0.006556 |
the `plan` and `apply` operations. In addition to uploading configurations and starting runs, you can use HCP Terraform's APIs to create and modify workspaces, edit variable values, and more. See the [API documentation](/terraform/cloud-docs/api-docs) for more details. | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/run/api.mdx | main | terraform | [
-0.022017434239387512,
0.003510167356580496,
0.01831471361219883,
0.023888785392045975,
-0.044634077697992325,
-0.0009253701427951455,
-0.06345144659280777,
-0.06311921775341034,
-0.030289635062217712,
0.11177391558885574,
-0.0423843152821064,
-0.03874310106039047,
0.052706360816955566,
-0... | 0.032236 |
# Run modes and options HCP Terraform runs support many of the same modes and options available in the Terraform CLI. ## Plan and Apply (Standard) The default run mode of HCP Terraform is to perform a plan and then apply it. If you have enabled auto-apply and are using a VCS or API workflow, a successful plan applies i... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/run/modes-and-options.mdx | main | terraform | [
-0.02304874174296856,
0.0420602485537529,
0.059731870889663696,
0.0031451652757823467,
-0.008304878138005733,
-0.02312651462852955,
-0.05245143175125122,
-0.06685500591993332,
0.024846086278557777,
0.07364488393068314,
-0.03802910074591637,
-0.06739185005426407,
0.030736291781067848,
-0.02... | 0.02151 |
Saved plans are ideal for interactive CLI workflows, where you can perform many exploratory plans and then choose one to apply, or for custom continuous integration workflows where the default run queue behavior isn't suitable. - \*\*CLI:\*\* Use `terraform plan -out ` to perform and save a plan, then use `terraform ap... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/run/modes-and-options.mdx | main | terraform | [
-0.0381152480840683,
0.06229327991604805,
0.03187571465969086,
-0.028930051252245903,
-0.03510836884379387,
0.014399653300642967,
-0.05746304616332054,
-0.06897305697202682,
0.002312152646481991,
0.03805175796151161,
-0.0632895678281784,
-0.07144483923912048,
0.04480931907892227,
-0.032142... | 0.032398 |
imply some additional limitations on HCP Terraform features for remote plans created with targeting: - [Sentinel](/terraform/cloud-docs/policy-enforcement) policy checks for targeted plans will see only the selected subset of resource instances planned for changes in [the `tfplan` import](/terraform/cloud-docs/policy-e... | https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/docs/cloud-docs/workspaces/run/modes-and-options.mdx | main | terraform | [
-0.0027099016588181257,
0.034395575523376465,
0.05357183516025543,
0.018630806356668472,
0.10829481482505798,
-0.024121800437569618,
0.025817502290010452,
-0.06523700803518295,
0.025978444144129753,
0.07537520676851273,
-0.03358243405818939,
-0.0785595029592514,
0.04615674167871475,
0.0034... | 0.021352 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.