…#97590)

Add version to binaries produced via patchGoModVendor to allow run-time provider
version validation by terraform.

This was initially introduced in 4e63119 (terraform: add the version component to terraform provider paths (NixOS#34497), 2018-02-06)
but broken in 3e5149a (terraform-providers: fix the google and google-beta providers, 2020-03-24)
for terraform-providers.google and terraform-providers.google-beta, and in 20f55a9 (terraform-providers.ibm: move to update-all script, 2020-04-26)
for terraform-providers.ibm.

(cherry picked from commit 94d2aeb)

0.6.0 added support for Fedora CoreOS Config v1.1.0.

 - Add Fedora CoreOS Config v1.1.0 support (NixOS#63)
 -  - Accept FCC v1.1.0 and output Ignition v3.1.0
 -  - Continue to support FCC v1.0.0 and output Ignition v3.0.0
 -  - Support merging FCC snippets into v1.0.0 or v1.1.0 FCC content
 -  - Note: Version skew among snippets and content is not supported
 - Change Container Linux Config to render Ignition v2.3.0 (NixOS#60)
 - Add zip archive format with signed checksum

(cherry picked from commit 8cdc34c)

(cherry picked from commit 063f1d7)

(cherry picked from commit 107707a)

Terraform 0.13 adopts a new filesystem layout for plugins (illustrated below).

Terraform 0.12 and earlier
`plugins-dir/terraform-provider-aws_v3.7.0`

Terraform 0.13
`plugins-dir/registry.terraform.io/hashicorp/aws/3.7.0/linux_amd64/terraform-provider-aws_v3.7.0`

To support all packaged Terraform versions a shim is created at both locations.

This approach was inspired by https://github.com/numtide/generate-terraform-provider-shim

Terraform 0.13 provider documentation https://www.terraform.io/upgrade-guides/0-13.html#new-filesystem-layout-for-local-copies-of-providers

layout terraform providers filesystem in withPlugins

(cherry picked from commit cd1b594)

(cherry picked from commit 60645f0)

(cherry picked from commit 87e21d1)

Added provider source address to providers hosted in the same GitHub
repository. Other providers have moved repository and would require a
patch to the package path.

(cherry picked from commit 72cd428)

We will be relying on the pname to figure out where to link the plugin.

(cherry picked from commit 3f49e5b)

Move the providerSourceAddress fallback to the terraform.withPlugins
function. Since plugins can be arbitrary derivations, there is no
guarantee that this attribute will be exposed.

While doing that I also cleaned the toDrv function to only pass
attributes to the builder which are required by the build.

The Terraform 0.13 fallback slug has changed from
`nixpkgs/<provider-owner>/<provider-name>` to `nixpkgs/<provider-name>`
as the owner is also not always available. As a nixpkgs user, all I know
is that the provider is in nixpkgs and his name, the owner information
is not necessarily easy to get by.

(cherry picked from commit c79ff8d)

(cherry picked from commit f5a8529)

(cherry picked from commit f7cf7ed)

(cherry picked from commit b0a0ffb)

https://github.com/hashicorp/terraform/releases/tag/v0.13.5
(cherry picked from commit 8b63613)

(cherry picked from commit c603dae)

…ixOS#103396)

When using `terraform.withPlugins (ps: [])` the returned derivation does
not expose the meta of the underlying package. This change inherits meta
from the terraform derivation in the wrapper derivation to expose it.

(cherry picked from commit 380337d)

(cherry picked from commit 1b5ee95)

(cherry picked from commit 0876f35)

(cherry picked from commit c02f2fc)

(cherry picked from commit 19fceb5)

https://github.com/hashicorp/terraform/releases/tag/v0.14.0
(cherry picked from commit 209bdc8)

(cherry picked from commit 2eade6c)

(cherry picked from commit 306ca0d)

(cherry picked from commit fb3f86c)

(cherry picked from commit 55dc437)

(cherry picked from commit 86adcfa)

(cherry picked from commit 1eaf05f)

(cherry picked from commit e50eb89)

(cherry picked from commit 005461a)

(cherry picked from commit 198a576)

(cherry picked from commit 82ae6fc)

(cherry picked from commit 1b413b1)

(cherry picked from commit 0fc3374)

(cherry picked from commit 0fb14ea)

(cherry picked from commit 688c8c0)

* terraform-providers: handle go modules

More and more terraform providers are switching from vendored
dependencies to Go modules.

Let's say that you update the "aws" provider and it fails. You can run
it again with:

    ./update-provider aws --vendor

Any package that has the "vendorSha256" key will be considered as a go
module package.

The script now also supports adding new providers by using the
<owner>/<repo> format. Eg:

     ./update-provider hetznercloud/hcloud --vendor

* address comment

Fixes NixOS#104667 (comment)

* support the null use-case

* escape provider name as well

* fix typo

(cherry picked from commit 5851c31)

(cherry picked from commit 48413ef)

(cherry picked from commit e1c709b)

This also changes the origin of the code. Hashicorp decided to stop
maintaining that provider and passed on the buck to cyrilgdn.

(cherry picked from commit 0dc2e6d)

(cherry picked from commit d413ba8)

+ https://github.com/hashicorp/terraform/releases/tag/v0.14.1
+ https://github.com/hashicorp/terraform/releases/tag/v0.14.2

(cherry picked from commit 9b2804b)

https://github.com/hashicorp/terraform/releases/tag/v0.14.3
(cherry picked from commit 51d0a41)

https://github.com/hashicorp/terraform/releases/tag/v0.12.30
(cherry picked from commit 81fe5e0)

https://github.com/hashicorp/terraform/releases/tag/v0.13.6
(cherry picked from commit aed53ea)

https://github.com/hashicorp/terraform/releases/tag/v0.14.4
(cherry picked from commit 61810aa)

(cherry picked from commit 88fd1ec)

(cherry picked from commit bbdad5f)

Slight modification to avoid picking up changes from commit a6ce00c

(cherry picked from commit 6a1bee3)