terraform/registry/response
Justin Campbell 495826444b plugin/discovery: Use GPG keys from Registry
When verifying the signature of the SHA256SUMS file, we have been
hardcoding HashiCorp's public GPG key and using it as the keyring.

Going forward, Terraform will get a list of valid public keys for a
provider from the Terraform Registry (registry.terraform.io), and use
them as the keyring for the openpgp verification func.
2018-11-20 14:09:16 -05:00
..
module.go remove models dependency from the regresp 2017-10-25 15:27:29 -04:00
module_list.go copy regsrc and response from registry repo 2017-10-25 14:11:33 -04:00
module_provider.go copy regsrc and response from registry repo 2017-10-25 14:11:33 -04:00
module_versions.go missed another models dep in the registry 2017-10-25 15:57:51 -04:00
pagination.go copy regsrc and response from registry repo 2017-10-25 14:11:33 -04:00
pagination_test.go copy regsrc and response from registry repo 2017-10-25 14:11:33 -04:00
provider.go registry: adding provider functions to registry client 2018-10-16 18:53:51 -07:00
provider_list.go registry: adding provider functions to registry client 2018-10-16 18:53:51 -07:00
redirect.go copy regsrc and response from registry repo 2017-10-25 14:11:33 -04:00
terraform_provider.go plugin/discovery: Use GPG keys from Registry 2018-11-20 14:09:16 -05:00
terraform_provider_test.go plugin/discovery: Use GPG keys from Registry 2018-11-20 14:09:16 -05:00