2400 Commits (8564e934aa57cc59459581ee06479879ebf41bf0)

Author	SHA1	Message	Date
Daniel Schmidt	4915bdf90c	fix comment ... Co-authored-by: Liam Cervante <liam.cervante@hashicorp.com>	2 years ago
Daniel Schmidt	ea0856bfe7	add a line of documentation to clarify	2 years ago
Eloi Perdereau	30505dd1bf	website docs: fix "Block Representation" for `provider schema -json` (#34653) ... * website docs: fix "Block Representation" for `provider schema -json` * Update website/docs/cli/commands/providers/schema.mdx --------- Co-authored-by: Radek Simko <radeksimko@users.noreply.github.com>	2 years ago
Daniel Schmidt	3211068f10	Merge pull request #34644 from hashicorp/document-provider-lock-using-cache ... document `-enable-plugin-cache` flag	2 years ago
Daniel Schmidt	18796d0dea	chore: clarify wording ... Co-authored-by: Liam Cervante <liam.cervante@hashicorp.com>	2 years ago
Daniel Schmidt	ae56655afe	chore: remove trailing whitespace from file path	2 years ago
Daniel Schmidt	6f76d2077a	chore: improve wording	2 years ago
Martin Atkins	884e1fb2a4	terraform: Plans can be "complete" and "applyable" ... These ideas are both already implied by some logic elsewhere in the system, but until now we didn't have the decision logic centralized in a single place that could therefore evolve over time without necessarily always updating every caller together. We'll now have the modules runtime produce its own boolean ruling about each characteristic, which callers can rely on for the mechanical decision-making of whether to offer the user an "approve" prompt, and whether to remind the user after apply that it was an incomplete plan that will probably therefore need at least one more plan/apply round to converge. The "Applyable" flag directly replaces the previous method Plan.CanApply, with equivalent logic. Making this a field instead of a method means that we can freeze it as part of a saved plan, rather than recalculating it when we reload the plan, and we can export the field value in our export formats like JSON while ensuring it'll always be consistent with what Terraform is using internally. Callers can (and should) still use other context in the plan to return more tailored messages for specific situations they already know about that might be useful to users, but with these flags as a baseline callers can now just fall back to a generic presentation when encountering a situation they don't yet understand, rather than making the wrong decision and causing something strange to happen. That is: a lack of awareness of a new rule will now cause just a generic message in the UI, rather than incorrect behavior. This commit mostly just deals with populating the flags, and then all of the direct consequences of that on our various tests. Further changes to actually make use of these flags elsewhere in the system will follow in later commits, both in this repository and in other repositories.	2 years ago
Daniel Schmidt	3e2291ae36	document `-enable-plugin-cache` flag	2 years ago
Daniel Schmidt	3a77065e69	add `issensitive` function ... This function can be used to check if a value is marked as sensitive or not within terraform. Closes #34572	2 years ago
Tom Bamford	5c259226e6	docs: azurerm backend doc fixups	2 years ago
Jared Holgate	d9ccdfb7d1	docs: improve azurerm backend docs (#34564) ... * Update azurerm backend docs * Use support note notation * Fix table format * Tidy and enhance * Tidy warnings * Improvements * Add comment to CLI option * Add warnings * Improve example resource names * Follow convention for warning * Update website/docs/language/settings/backends/azurerm.mdx Co-authored-by: Luke Taylor <77284962+luke-taylor@users.noreply.github.com> * Update website/docs/language/settings/backends/azurerm.mdx Co-authored-by: Luke Taylor <77284962+luke-taylor@users.noreply.github.com> * Update website/docs/language/settings/backends/azurerm.mdx Co-authored-by: Luke Taylor <77284962+luke-taylor@users.noreply.github.com> * Update website/docs/language/settings/backends/azurerm.mdx Co-authored-by: Luke Taylor <77284962+luke-taylor@users.noreply.github.com> * Update website/docs/language/settings/backends/azurerm.mdx Co-authored-by: Luke Taylor <77284962+luke-taylor@users.noreply.github.com> * Update website/docs/language/settings/backends/azurerm.mdx Co-authored-by: Luke Taylor <77284962+luke-taylor@users.noreply.github.com> * Update website/docs/language/settings/backends/azurerm.mdx Co-authored-by: Luke Taylor <77284962+luke-taylor@users.noreply.github.com> * Update website/docs/language/settings/backends/azurerm.mdx Co-authored-by: Luke Taylor <77284962+luke-taylor@users.noreply.github.com> * Update website/docs/language/settings/backends/azurerm.mdx Co-authored-by: Luke Taylor <77284962+luke-taylor@users.noreply.github.com> * Apply suggestions from code review --------- Co-authored-by: Luke Taylor <77284962+luke-taylor@users.noreply.github.com> Co-authored-by: Tom Bamford <tom@bamford.io>	2 years ago
Brian Flad	3b4964270f	internal/command/jsonprovider: Remove root jsonfunction object from function output (#34536) ... Previously, the `providers schema -json` output would include the root object from `metadata functions -json`. This object had its own `format_version` property, which would be confusing with the root `format_version` property already present. This change still uses the `jsonfunction` package for consistency between cty and provider function JSON handling, but removes that extra object, instead making `functions` directly a mapping of names to signatures/definitions. This also adds a code comment to hint maintainers that jsonprovider format versioning is tied to jsonfunction format versioning. Example output prior to change: ```jsonc { "format_version": "1.0", "provider_schemas": { "registry.terraform.io/bflad/framework": { // ... "functions": { "format_version": "1.0", "function_signatures": { "example": { "description": "Echoes given argument as result", "summary": "Example function", "return_type": "string", "parameters": [ { "name": "input", "description": "String to echo", "type": "string" } ] } } } } } } ``` Example output after change: ```jsonc { "format_version": "1.0", "provider_schemas": { "registry.terraform.io/bflad/framework": { // ... "functions": { "example": { "description": "Echoes given argument as result", "summary": "Example function", "return_type": "string", "parameters": [ { "name": "input", "description": "String to echo", "type": "string" } ] } } } } } ```	2 years ago
Brian Flad	1298fcd412	Add missing function deprecation_message to JSON output and website documentation (#34520) ... Reference: https://github.com/hashicorp/terraform/pull/34450	2 years ago
Liam Cervante	ce16e1a68a	Complete upgrade guide for v1.7 (#34514) ... * complete 1.7 upgrade guide * also call out state interoperability * Update website/docs/language/upgrade-guides/index.mdx Co-authored-by: kmoe <5575356+kmoe@users.noreply.github.com> * actually fix dangling v1.6 references --------- Co-authored-by: kmoe <5575356+kmoe@users.noreply.github.com>	2 years ago
Graham Davison	bf4f36a3b7	tabs vs spaces	2 years ago
Graham Davison	0ff0ad8ce4	Updates documentation on IAM permissions with workspaces	2 years ago
Graham Davison	86da6ef19a	Adds section on storage locations	2 years ago
Graham Davison	02fadba041	Corrects path	2 years ago
Graham Davison	9d8ff095c0	Formatting	2 years ago
Brian McClain	35d6af0759	Test mocks docs fixes (#34435) ... * Update example with valid bucket name * quote alias name in provider block	2 years ago
Brandon Croft	2973d070b3	Merge pull request #34358 from hashicorp/brandonc/bump_go-slug_0.13.3 ... Bump go-slug to 0.13.3 and add .terraformignore guidelines	2 years ago
Pratik Thakare	98da7f49ce	Update website/docs/language/state/purpose.mdx ... Co-authored-by: Rose M Koron <32436232+rkoron007@users.noreply.github.com>	2 years ago
Brandon Croft	48aed874f8	Bump go-slug to 0.13.3 and add .terraformignore guidelines	2 years ago
KryptoBlack	349c80b50c	refact: removed ambiguous reference from purpose of terraform state	2 years ago
Graham Davison	29708f0784	Documents `AWS_ENDPOINT_URL` environment variable and endpoints configured in shared config files	2 years ago
kmoe	56bf889093	website: removed block docs (#34339) ... * website: removed block docs * website: link to removed block from state rm	2 years ago
Liam Cervante	5cbf7c5f96	Add docs for automatic var files in test directories (#34349)	2 years ago
Jared Baker	4729af3ccf	Merge pull request #34337 from hashicorp/s3/use_legacy_workflow-deprecation ... backend/s3: default `use_legacy_workflow` to false, deprecate	2 years ago
James Bardin	60ab95d3a7	Merge pull request #34348 from hashicorp/jbardin/import-for-each-docs ... add basic import for_each docs	2 years ago
James Bardin	4ae531c8a1	add basic import for_each docs	2 years ago
Craig Wright	5153465e00	Merge pull request #34311 from zhimsel/cidrhost-negative-docs	2 years ago
Craig Wright	9cb86ef1b9	Merge pull request #34299 from summera/custom-condition-doc-correction	2 years ago
Liam Cervante	89c1d06f05	Add documentation for the mocking functionality (#34198) ... * Add documentation for the new mocking functionality * add example for repeated blocks * validate providers * Apply suggestions from code review Co-authored-by: kmoe <5575356+kmoe@users.noreply.github.com> * address comments * tf fmt all examples * edits * fix typos --------- Co-authored-by: kmoe <5575356+kmoe@users.noreply.github.com> Co-authored-by: Brian McClain <brianmmcclain@gmail.com>	2 years ago
Jared Baker	38acde89e3	website: s3 backend upgrade guide for 1.7.0	2 years ago
Martin Atkins	7055650270	terraform console: Option to evaluate in a planned state ... Previously "terraform console" always evaluated in a kinda strange context where resource instance data comes from the prior state, but other derived of values end up being calculated dynamically based on the current configuration, which is okay for simple cases but can be confusing if the configuration has changed significantly since the most recent apply, or if there haven't yet been any applied changes. Now we'll allow an optional new mode where Terraform runs the normal plan phase (as if running "terraform plan") and then uses the resulting _planned state_ as the basis for evaluation, allowing evaluation against a partial approximation of what the world ought to look like if these changes were applied, without having to actually apply them first. As with the previous use of the eval walk, it's possible that an erroneous situation will still produce a partial evaluation scope, and so the console still allows evaluation against that scope but with a caveat that it might produce unexpected results. In practice this can be useful for debugging situations like when unknown values block planning of an object, to allow inspection of the values that are contributing to that blocked planning operation even though the plan is not yet complete.	2 years ago
Jared Baker	470a851e45	backend/s3: default use_legacy_workflow to false, deprecate ... In Terraform 1.7 we'll begin phasing out the legacy credential chain evaluation order by defaulting use_legacy_workflow to false and deprecating the argument. This will bring the default behavior into alignment with the AWS SDKs and CLI. Practitioners can still preserve the legacy behavior by setting this argument to `true`. In Terraform 1.8 this argument will be removed, and the S3 backend will always use the default credential chain evaluation order from the AWS SDK for Go.	2 years ago
Liam Cervante	0f94e1e7ab	docs: update terraform test docs with provider to run block reference examples (#34332) ... * docs: update terraform test docs with examples on provider to run block references * undo weird formatting	2 years ago
Liam Cervante	6670ab43f7	terraform test: rearrange the order of destroy operations (#34293)	2 years ago
Martin Atkins	844b1616e8	command/graph: Simpler resource-only graph by default ... Unless a user specifically requests a real operation graph using the -type option, we'll by default present a simplified graph which only represents the relationships between resources, since resources are the main side-effects and so the ordering of these is more interesting than the ordering of Terraform's internal implementation details.	2 years ago
Zach Himsel	2361c5dc98	Document negative host numbers for cidrhost() ... This feature was introduced in https://github.com/hashicorp/terraform/pull/13765 (and documented there), but it seems that its documentation was not carried over when the docs were reorganized.	2 years ago
Ari Summer	d12984064a	Correct EC2 instance encryption condition example in custom-conditions.mdx	2 years ago
kmoe	33dfeecbee	docs: more detail on import IDs (#34153)	2 years ago
kmoe	ccb5596742	website: add "importing" to json plan format docs (#34269)	2 years ago
Rose M Koron	5d9c1d4f8a	Update oci_core_instance links (#34257)	2 years ago
Johnny Lee-Othon	1f9734619f	Update machine-readable-ui.mdx (#34217) ... Added "import" under values of "action" for "planned_change".	2 years ago
sebhcp	2d381c050a	docs: add backend limitation (#31607) ... --------- Co-authored-by: sebhcp <sebhcp@users.noreply.github.com> Co-authored-by: Laura Pacilio <83350965+laurapacilio@users.noreply.github.com>	2 years ago
Graham Davison	4df60b4b90	Adds `https_proxy` and `no_proxy` parameters	2 years ago
Graham Davison	fce0cf6d9c	Adds support for `sso` endpoint override	2 years ago
Liam Cervante	1974c9ec16	docs: add explicit instruction for windows filepaths (#34193) ... * docs: add explicit instruction for windows filepaths * fix you/we/Terraform usage	2 years ago