From 24ced6bbcab006ed9944fe7d544f7184832f8432 Mon Sep 17 00:00:00 2001 From: Alisdair McDiarmid Date: Wed, 15 Apr 2020 14:28:34 -0400 Subject: [PATCH] Update CHANGELOG.md --- CHANGELOG.md | 1 + 1 file changed, 1 insertion(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index 590591dbb..66139ea99 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -23,6 +23,7 @@ ENHANCEMENTS: * core: added support for passing metadata from modules to providers using HCL [GH-22583] * core: significant performance enhancements for graph operations, which will help with highly-connected graphs [GH-23811] * command/state: Add state replace-provider subcommand to allow changing the provider source for existing resources [GH-24523] +* lang: Add "sum" function, which takes a list or set of numbers and returns the sum of all elements [GH-24666] * Terraform CLI now supports TLS 1.3 and supports Ed25519 certificates when making outgoing connections to remote TLS servers. While both of these changes are backwards compatible in principle, certain legacy TLS server implementations can reportedly encounter problems when attempting to negotiate TLS 1.3. (These changes affects only requests made by Terraform CLI itself, such as to module registries or backends. Provider plugins have separate TLS implementations that will gain these features on a separate release schedule.) * On Unix systems where `use-vc` is set in `resolv.conf`, Terraform will now use TCP for DNS resolution. We don't expect this to cause any problem for most users, but if you find you are seeing DNS resolution failures after upgrading please verify that you can either reach your configured nameservers using TCP or that your resolver configuration does not include the `use-vc` directive.