This was created in a few steps. "go" in the following is go 1.11-rc1

- Use "go mod init" to migrate the vendor/vendor.json references into
  a new go.mod.

- rm -rf vendor, since we're going to reconstruct that again in a moment.

- "go mod tidy" as a way to get all the necessary stuff installed and the
  go.mod updated for what was actually resolved.

- "go mod vendor" copied all of the dependencies from the module cache
  into the "vendor" directory, and created the `vendor/modules.txt` index
  file.

This can then be built using "go install -mod=vendor .", where that extra
flag forces it to read the dependencies only from the vendor dir and not
from upstream or the local cache.

This is not intended to be merged: it was just an experiment to test out
Go 1.11-rc1 and get a sense of what a transition here might look like.

Adding TFE v2 provider links

pretty-print json in http requests/responses

Here our prior existing single template becomes the "Bug report" template,
and we introduce a second "Feature request" template that is more
appropriate for gathering context about a feature request.

backend/remote: do not use the TFE_TOKEN env variable

Instead promote the use of shared credentials using the CLI Config File

update master branch with provider links

backend/remote: use schema max/min items options

backend/remote: add a new backend for storing state and running operations remotely

By adding this method you now only have to pass a `*disco.Disco` object around in order to do discovery and use any configured credentials for the discovered hosts.

Of course you can also still pass around both a `*disco.Disco` and a `auth.CredentialsSource` object if there is a need or a reason for that!

It’s a purely cosmetic change, but I find it easier to read them like this.

Just providing the hostname won't work. This commit adds an example and fixes
the explanation.

help: Make version and help flags consistent

These flags are presented as POSIX/GNU-style long-form flags
(double-dash), whereas the rest of our CLI flags as seen in sub-commands
are presented as single-dash options.

While both work in both cases (on part of the flag package allowing
double dashes as well), we converge around the single-dash form, so the
basic help text here should be consistent.

website: Correcting terraform custom provider name in community-index.html.markdown

helper/resource: Add ability to pre-taint resources

Corrected the naming of the 'Keboola' provider and shifted it down to keep alphabetical ordering.

It's been a while since we made any significant updates to this page.
The main theme of this revamp is to ensure that we highlight how to
provide "ambient credentials" for each of the module sources using the
standard mechanisms for each source type.

While there, I also attempted a general cleanup to highlight the main
cases and make this less like a detailed description of all of
go-getter's esoteric features, and did some general copy-editing to write
it in our usual documentation "voice".

vendor: terraform-providers/terraform-provider-aws@v1.29.0 and aws/aws-sdk-go@v1.14.31

vendor: Pin aws/aws-sdk-go/service/lexmodelbuildingservice@v1.13.28 and aws/aws-sdk-go/service/organizations@v1.13.28 in vendor.json for consistency