terraform

Commit Graph

Author	SHA1	Message	Date
Martin Atkins	9b57a43bde	website: First draft of Terraform v1.8 upgrade guide We may revise this further during the Terraform v1.8 prerelease period, if feedback suggests that more information is needed or that this information is not clear enough. The main goal here is just to get out of the confusing situation where the v1.8 branch contains a v1.7 upgrade guide, so that we can link to the upgrade guide from the changelog. The full upgrade guide page gives us room for more details, allowing the changelog to serve just as a concise list of changes.	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
Jared Baker	38acde89e3	website: s3 backend upgrade guide for 1.7.0	2 years ago
Graham Davison	30928097ee	Updates deprecation documentation	3 years ago
Graham Davison	cf3d51665b	Removes references to reconfiguring backend	3 years ago
Graham Davison	04ac7c571d	Fixes to documentation Co-authored-by: Jared Baker <jar-b@users.noreply.github.com>	3 years ago
Graham Davison	59b371cba0	Fixes URL	3 years ago
Graham Davison	e39a39ae53	Fixes spelling	3 years ago
Graham Davison	088c307c1f	Updates documentation to indicate that changes to backend may require reconfiguring backend	3 years ago
Liam Cervante	487eeda94e	[testing framework] Add documentation (#33454 ) * [terraform test] add docs * Apply suggestions from code review Co-authored-by: Rose M Koron <32436232+rkoron007@users.noreply.github.com> * polish remaining comments * Apply suggestions from code review Co-authored-by: Rose M Koron <32436232+rkoron007@users.noreply.github.com> * address remaining comments * typo * update verbose machine readable docs * standardise new JSON field names --------- Co-authored-by: Rose M Koron <32436232+rkoron007@users.noreply.github.com>	3 years ago
Martin Atkins	a0b3a2f49c	website: Terraform v1.5 upgrade guide (#33285 ) There aren't any super significant upgrade considerations this time, so this is really just a summary of the two main entries in the changelog. There is also an entry in the changelog about ending support for older versions of Windows, but in that case we are just passing on a release note from Go itself and we already warned against using versions earlier than Windows 10 back in Terraform v0.15 (since we are relying on the Windows 10 console API) and so this is just one additional reason why Terraform might not work correctly on those earlier versions of Windows, so not worth mentioning in the upgrade guide here since our guidance hasn't changed.	3 years ago
Bryce Kalow	6b35927cf0	docs: fix up content issues, add content-check command (#32869 )	3 years ago
Omar Ismail	bea8ad355c	website: v1.4 upgrade guide more guidance on who is affected by the provider cache change	3 years ago
Omar Ismail	189820b6ea	Terraform v1.4 Upgrade Guide	3 years ago
Martin Atkins	a30294372f	website: Version-specific upgrade guides (v1.4 branch) Before our website allowed selecting from older versions of Terraform to see older documentation we needed to preserve all of the historical upgrade guides in the latest release branch so that they'd stay available on the website. However, our new strategy is for each release to have its own separate set of documentation selectable using a global version selector. We should therefore now have only the upgrade guide for the each minor release on its release branch, with the upgrade guides for earlier releases instead maintained on their own branches. However, our v1.1 branch is, as a matter of pragmatism, serving as the home for the "v1.1 and earlier" documentation, and so there will continue to be multiple upgrade guides on that branch. For that reason, we're preserving the URL scheme "upgrade-guides" (plural) even though the URL now points to only a single version upgrade guide because that causes readers to land in the correct place if they are on a modern version's upgrade guide page and they use the version selector to choose the "v1.1 and earlier" option.	4 years ago
Dylan Staley	21cbb5b392	migrate docs to mdx	4 years ago

16 Commits (d3b8a55781f42b5fab662e2a4f2dc2b77faeef1a)