15 Commits (2b4101fdff6a2fc575e123134bf5c8e321c34921)

Author	SHA1	Message	Date
James Bardin	b6c409613e	make all unnecessary edges dotted ... There were a couple missing	6 years ago
James Bardin	1c1782bb1b	add lists of operations	6 years ago
James Bardin	dcf62ed378	Fix typo and add more information about CBD ... The reason for the interleaved updated in CBD is important. fix	6 years ago
James Bardin	fb9c8261c5	replace the incorrect graph image ... The dot in the comment was correct, so it was just the wrong image saved.	6 years ago
James Bardin	16b7541277	Apply suggestions from code review ... Co-authored-by: Alisdair McDiarmid <alisdair@users.noreply.github.com>	6 years ago
James Bardin	642dadcd96	add doc about destroying resources and ordering	6 years ago
Kyler Middleton	89bef596fc	docs: Fix typo in maintainer-etiquette (#24609)	6 years ago
Paddy	e6592dc710	Add support for provider metadata to modules. (#22583) ... Implement a new provider_meta block in the terraform block of modules, allowing provider-keyed metadata to be communicated from HCL to provider binaries. Bundled in this change for minimal protocol version bumping is the addition of markdown support for attribute descriptions and the ability to indicate when an attribute is deprecated, so this information can be shown in the schema dump. Co-authored-by: Paul Tyng <paul@paultyng.net>	6 years ago
Martin Atkins	39e609d5fd	vendor: switch to HCL 2.0 in the HCL repository ... Previously we were using the experimental HCL 2 repository, but now we'll shift over to the v2 import path within the main HCL repository as part of actually releasing HCL 2.0 as stable. This is a mechanical search/replace to the new import paths. It also switches to the v2.0.0 release of HCL, which includes some new code that Terraform didn't previously have but should not change any behavior that matters for Terraform's purposes. For the moment the experimental HCL2 repository is still an indirect dependency via terraform-config-inspect, so it remains in our go.sum and vendor directories for the moment. Because terraform-config-inspect uses a much smaller subset of the HCL2 functionality, this does still manage to prune the vendor directory a little. A subsequent release of terraform-config-inspect should allow us to completely remove that old repository in a future commit.	6 years ago
Martin Atkins	e1af10b554	docs: README for the plugin-protocol directory ... This is an initial partial description of the plugin protocol focused mainly on explaining the purpose of the .proto files. In subsequent updates we will also document the negotiation protocol, etc. For this first pass the goal was just to publish some information that was already available in an internal design document so that it's visible to SDK implementers. It is focused on the .proto versioning strategy because that was the main topic of the internal design documentation this was based on.	7 years ago
James Bardin	fa1f9be539	add tfplugin proto docs files ... Add versioned tfplugin proto files to the docs directory, for easier reference. The latest version starts as a symlink to the current file used for generated the tfplugin package in ./internal/tfplugin5. When changing the protocol version, the old file must be copied to ./docs/plugin-protocol/, and a new symlink created for the latest version.	7 years ago
Martin Atkins	1f241f8f83	docs: Some updates to the architecture summary ... This doc was originally written in the middle of Terraform v0.12 development while some refactoring was already in progress. Here we update those parts to refer to where the relevant functionality finally landed, and also update some things that we did not anticipate changing at the time but ended up having to be changed during the v0.12 development anyway.	7 years ago
Martin Atkins	18c88f5a41	docs: Import some existing docs to bootstrap the codebase docs section ... For a while now we've been gathering some codebase-level docs that felt out-of-place on the main Terraform website (since they are about the implementation, not usage) but we had no existing suitable place to put them. In order to make this information more available (and, hopefully, more likely to stay up-to-date as we change things), here we'll establish the "docs" directory as a place to keep documentation aimed at those who are working on code changes to the Terraform Core codebase. User-oriented docs should never appear in this directory. The Terraform website is always the better place for those. The set of docs here is rudimentary to start and we'll see if it makes sense to expand and reorganize it over time based on the experience with having these initial docs available.	7 years ago
Julien Pivotto	a4f4c70c60	mons-months: fix typo in maintainer-etiquette	9 years ago
Radek Simko	df26c5460c	docs: Add Maintainer's etiquette	9 years ago