From a1a976c720aa9d568471bbe1f7b714ab91bdf285 Mon Sep 17 00:00:00 2001 From: Joe Harrison Date: Tue, 11 Oct 2022 20:28:28 +0100 Subject: [PATCH] Document provider registry response property shasum Add a short summary of the `shasum` property in the Provider Registry Protocol's distribution package response documentation. The Response Properties section of the provider registry protocol does not mention the `shasum` property, but it is required and shown in the example. --- website/docs/internals/provider-registry-protocol.mdx | 3 +++ 1 file changed, 3 insertions(+) diff --git a/website/docs/internals/provider-registry-protocol.mdx b/website/docs/internals/provider-registry-protocol.mdx index dc260e41d5..cd04842314 100644 --- a/website/docs/internals/provider-registry-protocol.mdx +++ b/website/docs/internals/provider-registry-protocol.mdx @@ -319,6 +319,9 @@ A successful result is a JSON object with the following properties: * `shasums_signature_url` (required): a URL from which Terraform can retrieve a binary, detached GPG signature for the document at `shasums_url`, signed by one of the keys indicated in the `signing_keys` property. + +* `shasum` (required): the SHA256 checksum for this provider's zip archive as + recorded in the "shasums" document. * `signing_keys` (required): an object describing signing keys for this provider package, one of which must have been used to produce the signature