10 Commits (094ed0ff4dc77b8b79bbf53861d9be602ea6216f)

Author	SHA1	Message	Date
Nick Fagerlund	6494591ec1	website: Remove extra copy of "Getting Started", update links ... This guide now lives at: - https://learn.hashicorp.com/terraform#getting-started ...and terraform.io has been redirecting to there for quite a while. This commit removes the extra copy so that the text of the two versions doesn't drift, and updates existing links to point to the new location.	6 years ago
Nick Fagerlund	ac45e43fda	website: Finish moving "writing custom providers" to /docs/extend/ ... This document was previously copied to the "Extending Terraform" section (in the terraform-website repo), and the old URL was redirected so that the copy in /guides can no longer be reached on the website. But the old copy of the file remained, and now it runs the risk of confusing contributors, since the copy in terraform-website/.../docs/extend is the more up-to-date version.	7 years ago
Nick Fagerlund	7d5db9522f	website: Fix plugin path on Windows (#19423) ... ...and one other reference to the application data directory. Context: https://docs.microsoft.com/en-us/windows/desktop/shell/knownfolderid#folderid_roamingappdata In newer Windows versions, the folder accessible as `%APPDATA%` (and via various APIs) is actually at something like "documents and settings\user\application data\roaming", while earlier versions omit the "\roaming" part of the path. This means you can confuse people by referring to the "application data" directory by its human name, because "roaming" is the real application data directory, but it looks like a subdirectory of "application data". Thus, it's less confusing to just use the `%APPDATA%` variable, with the added benefit that you can copy and paste the path and it'll just work in most places.	7 years ago
Nick Fagerlund	b3935b29d7	website: Reconcile docs about plugin discovery and downloading (#18973) ... website: Reconcile docs about plugin discovery and downloading I'm attempting to keep things simple for normal users while making sure we've got the full behavior written down somewhere for plugin developers. This commit doesn't stand alone; it's paired with a commit in the terraform-website repo, to deal with some related content in the "extend" section.	7 years ago
Radek Simko	ecac80fd8e	docs: Fix inaccurate plugin CRUD description	8 years ago
Martin Atkins	f19bf25945	website: don't recommend "providers" block in CLI config ... This mechanism for configuring plugins is now deprecated, since it's not capable of declaring plugin versions. Instead, we recommend just placing plugins into a particular directory, which is now documented on the main providers documentation page and linked from the more detailed docs on plugins in general.	9 years ago
Clint	e2272f71a0	Update our documentation to push "Getting Started" better (#15866) ... * update plugin/provider to make clear this section isn't needed for regular use * add some links and notes about getting started * remove the mention of binaries... I 'm not sure it's needed yet * 'Installing Terraform Providers' section * sometimes I can't words good * move the 'installing providers' block * cleanup of terms * copy that update to plugins/provider too	9 years ago
Nick Fagerlund	8c7bfde292	Docs: Fix broken links and a broken example ... These links were casualties of the core/provider split. There was also an example that suggested cloning a subdirectory of a git repo.	9 years ago
Martin Atkins	c57dbebe84	documentation: explain provider dev environment setup ... The intent here is just to introduce some initial docs on our recommended way to develop plugins in the same GOPATH as Terraform itself. The documentation in this area needs some more fundamental rework as it is rather outdated and mis-organized, but that's outside the scope of what this change is trying to achieve.	9 years ago
Martin Atkins	7ed70bb00e	website: new filesystem layout for core/provider split ... This repo now contains only the core docs, with other content moving elsewhere.	9 years ago