github.com/aclaygray/packer@v1.3.2/website/source/docs/post-processors/checksum.html.md (about) 1 --- 2 description: | 3 The checksum post-processor computes specified checksum for the artifact list 4 from an upstream builder or post-processor. All downstream post-processors 5 will see the new artifacts. The primary use-case is compute checksum for 6 artifacts allows to verify it later. So firstly this post-processor get 7 artifact, compute it checksum and pass to next post-processor original 8 artifacts and checksum files. 9 layout: docs 10 page_title: 'Checksum - Post-Processors' 11 sidebar_current: 'docs-post-processors-checksum' 12 --- 13 14 # Checksum Post-Processor 15 16 Type: `checksum` 17 18 The checksum post-processor computes specified checksum for the artifact list 19 from an upstream builder or post-processor. All downstream post-processors will 20 see the new artifacts. The primary use-case is compute checksum for artifact to 21 verify it later. 22 23 After computes checksum for artifacts, you can use new artifacts with other 24 post-processors like 25 [artifice](https://www.packer.io/docs/post-processors/artifice.html), 26 [compress](https://www.packer.io/docs/post-processors/compress.html), 27 [docker-push](https://www.packer.io/docs/post-processors/docker-push.html), 28 or a third-party post-processor. 29 30 ## Basic example 31 32 The example below is fully functional. 33 34 ``` json 35 { 36 "type": "checksum" 37 } 38 ``` 39 40 ## Configuration Reference 41 42 Optional parameters: 43 44 - `checksum_types` (array of strings) - An array of strings of checksum types 45 to compute. Allowed values are md5, sha1, sha224, sha256, sha384, sha512. 46 - `output` (string) - Specify filename to store checksums. This defaults to 47 `packer_{{.BuildName}}_{{.BuilderType}}_{{.ChecksumType}}.checksum`. For 48 example, if you had a builder named `database`, you might see the file 49 written as `packer_database_docker_md5.checksum`. The following variables are 50 available to use in the output template: 51 52 - `BuildName`: The name of the builder that produced the artifact. 53 - `BuilderType`: The type of builder used to produce the artifact. 54 - `ChecksumType`: The type of checksums the file contains. This should be 55 used if you have more than one value in `checksum_types`.