website: Forward-port docs on file-hashing functions from 0.11 branch

This commit is contained in:
Martin Atkins 2019-02-13 16:10:14 -08:00
parent fedbd6c3b8
commit b4d9f63622
1 changed files with 9 additions and 0 deletions

View File

@ -437,6 +437,15 @@ The supported built-in functions are:
of the key used to encrypt their initial password, you might use: of the key used to encrypt their initial password, you might use:
`zipmap(aws_iam_user.users.*.name, aws_iam_user_login_profile.users.*.key_fingerprint)`. `zipmap(aws_iam_user.users.*.name, aws_iam_user_login_profile.users.*.key_fingerprint)`.
The hashing functions `base64sha256`, `base64sha512`, `md5`, `sha1`, `sha256`,
and `sha512` all have variants with a `file` prefix, like `filesha1`, which
interpret their first argument as a path to a file on disk rather than as a
literal string. This allows safely creating hashes of binary files that might
otherwise be corrupted in memory if loaded into Terraform strings (which are
assumed to be UTF-8). `filesha1(filename)` is equivalent to `sha1(file(filename))`
in Terraform 0.11 and earlier, but the latter will fail for binary files in
Terraform 0.12 and later.
## Templates ## Templates
Long strings can be managed using templates. Long strings can be managed using templates.