Update CHANGELOG.md
This commit is contained in:
parent
320fcf4942
commit
3fc3cba66d
|
@ -24,9 +24,10 @@ ENHANCEMENTS:
|
||||||
* core: significant performance enhancements for graph operations, which will help with highly-connected graphs [GH-23811]
|
* 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]
|
* 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]
|
* lang: Add "sum" function, which takes a list or set of numbers and returns the sum of all elements [GH-24666]
|
||||||
|
* cli: When installing providers from the Terraform Registry, Terraform will verify the trust signature for partner providers, and allow for self-signed community providers [GH-24617]
|
||||||
|
* cli: It is now possible to optionally specify explicitly which installation methods can be used for different providers, such as forcing a particular provider to be loaded from a particular directory on local disk instead of consulting its origin provider registry. [GH-24728]
|
||||||
* 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.)
|
* 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.
|
* 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.
|
||||||
* When installing providers from the Terraform Registry, verify the trust signature for partner providers, and add support for self-signed community providers [GH-24617]
|
|
||||||
|
|
||||||
BUG FIXES:
|
BUG FIXES:
|
||||||
* backend/oss: Allow locking of multiple different state files [GH-24149]
|
* backend/oss: Allow locking of multiple different state files [GH-24149]
|
||||||
|
|
Loading…
Reference in New Issue