30525 Commits (4835deddaef450198bba00a50311f2ada6f79b96)

 

All Branches   

Search

Author	SHA1	Message	Date
Corey Innis	4835deddae	tiny update to Resource Addressing: "value4" ... An almost ridiculous contribution. Yet, it made it so much clearer for me, when I realized I could frame it with this finish.	4 years ago
James Bardin	730756eca2	Merge pull request #32051 from hashicorp/jbardin/destroy-checkable-outputs ... Clean up handling of check-related graph nodes	4 years ago
HashiBot	54de574e2b	chore: Update Digital Team Files (#32037) ... * Update generated scripts (website-start.sh) * Update generated website Makefile * Update generated scripts (should-build.sh) * Update generated scripts (website-build.sh) * chore: update root `Makefile` Co-authored-by: Kevin Wang <kwangsan@gmail.com>	4 years ago
James Bardin	92c8c76684	fix variable name	4 years ago
James Bardin	a44c859c86	update UIMode comment	4 years ago
Kevin Wang	03e262a70b	chore: rewrite internal redirects (#32038)	4 years ago
James Bardin	ac99cd6051	remove extra import line	4 years ago
James Bardin	28d5a5bf63	NoOp nodes should not have destroy edges ... NoOp changes should not participate in a destroy sequence, but because they are included as normal update nodes the usual connections were still being made.	4 years ago
James Bardin	586401aeea	make naming consistent	4 years ago
James Bardin	8a4883fd13	don't eval checks on destroy	4 years ago
James Bardin	8d11c7f524	the destroy refresh plan should be refresh-only ... Refreshing for a destroy should use the refresh-only plan to avoid planning new objects or evaluating conditions. This should also be skipped if there is no state, since there would be nothing to refresh.	4 years ago
James Bardin	08081097cb	check console with preconditions	4 years ago
James Bardin	a0723442b9	test for incorrectly evaluated outputs	4 years ago
James Bardin	333bdecf39	checks must be registered during eval	4 years ago
James Bardin	1eb22fd94a	fix output transformer names ... The removeRootOutputs field was not strictly used for that purpose, and was also copied to another DestroyPlan field.	4 years ago
James Bardin	47b6386348	remove IsFullDestroy workaround ... IsFullDestroy was a workaround during apply to detect when the change set was created by a destroy plan. This no longer works correctly, and we need to fall back to the UIMode set in the plan.	4 years ago
James Bardin	bcb792ee00	complete the root output expansion ... Not all root output instances were going through proper expansion when destroy operations were involved, leading to cases where they would be evaluated even though the expected result was only to remove them from the state. Normally destroy nodes stand alone in the graph, and do not produce references to other nodes. Because root output nodes were replaced by expansion nodes, these were being connected via normal references, even in the case where we were working with a destroy graph.	4 years ago
James Bardin	8a24d73d15	outputs should not be checked during destroy ... Module output may need to be evaluated during destroy in order to possibly be used by providers. The final state however is that all objects are destroyed, so preconditions should not be evaluated.	4 years ago
James Bardin	71837d187b	walkDestroy op in apply graph	4 years ago
James Bardin	5085ccdfbd	fix error message	4 years ago
Liam Cervante	ab8a3f7063	Update go-cty to latest version (#32033) ... * Update go-cty to latest version * go mod tidy	4 years ago
James Bardin	713421c3ab	Merge pull request #31908 from hashicorp/bump_net ... go get -u golang.org/x/net	4 years ago
Craig Wright	ae4a8ba77b	Fixing a bug introduced in the review process.	4 years ago
Craig Wright	1650bb9892	Merge pull request #31951 from hashicorp/docs-issue-form ... Add Documentation Issue form template	4 years ago
Craig Wright	d40b5c7755	Update .github/ISSUE_TEMPLATE/documentation_issue.yml ... Co-authored-by: Judith Malnick <judith.patudith@gmail.com>	4 years ago
Laura Pacilio	58ad930f2d	Revert "more content updates for flow" ... This reverts commit 84edd84471.	4 years ago
Laura Pacilio	cb975a5fff	Revert "Remove future-facing statements" ... This reverts commit 0a7e221a49.	4 years ago
Laura Pacilio	84edd84471	more content updates for flow	4 years ago
Laura Pacilio	0a7e221a49	Remove future-facing statements	4 years ago
James Bardin	99608b7da4	Merge pull request #32002 from hashicorp/compliance/add-license ... [COMPLIANCE] Update MPL 2.0 LICENSE	4 years ago
Martin Atkins	4bc1696fd1	core: Simplify our idea of "root node" and require it for DynamicExpand ... The graph walking mechanism is specified as requiring a graph with a single root, which in practice means there's exactly one node in the graph which doesn't have any dependencies. However, we previously weren't verifying that invariant is true for subgraphs returned from DynamicExpand. It was working anyway, but it's not ideal to be relying on a behavior that isn't guaranteed by our underlying infrastructure. We also previously had the RootTransformer being a bit clever and trying to avoid adding a new node if there is already only a single graph with no dependencies. That special case isn't particularly valuable since there's no harm in turning a one-node graph into a two-node graph with an explicit separate root node, and doing that allows us to assume that the root node is always present and is always exactly terraform.rootNode. Many existing DynamicExpand implementations were not producing valid graphs and were previously getting away with it. All of them now produce properly-rooted graphs that should pass validation, and we will guarantee that with an explicit check of the DynamicExpand return value before we try to walk that subgraph. For good measure we also verify that the root node is exactly terraform.rootNode, even though that isn't strictly required by our graph walker, just to help us catch potential future bugs where a DynamicExpand implementation neglects to add our singleton root node.	4 years ago
Brian Flad	8c93420270	docs/plugin-protocol: Add notes about missing configuration in ReadResource and UpgradeResourceState request messages (#31998) ... This opts to inline document these intentional design decisions in the protocol definition as a catch-all for it not being documented elsewhere. Protocol Buffers files updated via: ```shell make protobuf ```	4 years ago
James Bardin	980bf430f3	Merge pull request #31990 from hashicorp/jbardin/orphan-noop ... core: A NoOp orphan change has nothing to apply	4 years ago
hashicorp-copywrite[bot]	dcee05d198	[COMPLIANCE] Update MPL 2.0 LICENSE	4 years ago
James Bardin	3779dbc2af	noop orphan change has nothing to apply ... An orphaned resource which plans as a NoOp change will have no config. This is not an error, but there is nothing to do since there are also no checks to validate. We still leave the change in the plan to keep the plan as complete as possible, noting all possible changes. Preventing the node from being added to the graph is awkward, because the config is attached separately from the diff transformer. This should not pose any problems however, because there is no longer any state or config linking the instance to any dependencies in the graph.	4 years ago
Sarah French	73c3994455	Update CHANGELOG.md	4 years ago
Sarah French	89ef27d3b4	Add Private Service Connect endpoint support to GCS backend (#31967) ... * Add support for `storage_custom_endpoint` in `gcs` backend * Add documentation for new `storage_custom_endpoint` endpoint * Empty commit to trigger Vercel deployment	4 years ago
Brandon Croft	bc1436af53	Merge pull request #31821 from glennsarti/gs/TF-707-add-pre-apply ... Add support for pre-apply task results in the cloud backend	4 years ago
Nick Fagerlund	71f1b12226	Merge pull request #31959 from hashicorp/nf/oct22-updown-comments ... Clarify some comments in internal/dag	4 years ago
Nick Fagerlund	ccd7bd017e	Clarify some comments in internal/dag ... When reading this code to check Terraform's graph sorting behavior, I got very confused about the direction of traversal for several methods. Although some of these methods would also probably benefit from renames, this commit only updates their doc comments to use the same directional terminology that we use in the `Edge` interface (source/target).	4 years ago
Craig Wright	a8d6d5c913	Correcting a line break visual issue.	4 years ago
Craig Wright	b1c720a633	Update .github/ISSUE_TEMPLATE/documentation_issue.yml ... Thanks! Co-authored-by: Judith Malnick <judith.patudith@gmail.com>	4 years ago
Craig Wright	f058392421	Apply suggestions from code review ... Thanks! Co-authored-by: Judith Malnick <judith.patudith@gmail.com>	4 years ago
Matthew Garrell	03bff99caa	Merge pull request #31954 from hashicorp/mg_no_code_prov_followup ... Adding mention of no-code to Creating Modules section of TF Language docs	4 years ago
Laura Pacilio	e60bfc0b57	Merge pull request #31953 from hashicorp/add-cont-valid-callout ... Add callout to Continuous Validation	4 years ago
Matthew Garrell	a50d8cfc11	Adding mention of no-code to Modules section of TF Language docs	4 years ago
Liam Cervante	4d7ba14f72	Add skeleton action for equivalence tests (#31940)	4 years ago
Laura Pacilio	c8d8536160	Add callout to Continuous Validation	4 years ago
Craig Wright	3afa9bd08e	Create documentation_issue.yml ... Closes https://github.com/hashicorp/terraform/issues/31552. Adds a new issue form type for documentation issues. Format discussed with docs team.	4 years ago
Laura Pacilio	1faa05b344	Merge pull request #31945 from hashicorp/fix-backends-link ... Update backends.mdx	4 years ago