Update CHANGELOG.md
This commit is contained in:
parent
c921c8580e
commit
6f04215cc0
|
@ -55,6 +55,7 @@ BUG FIXES:
|
||||||
* cli: The `terraform plan` command (and the implied plan run by `terraform apply` with no arguments) will now print any warnings that were generated even if there are no changes to be made. [GH-24095]
|
* cli: The `terraform plan` command (and the implied plan run by `terraform apply` with no arguments) will now print any warnings that were generated even if there are no changes to be made. [GH-24095]
|
||||||
* cli: When using the `TF_CLI_CONFIG_FILE` environment variable to override where Terraform looks for CLI configuration, Terraform will now ignore the default CLI configuration directory as well as the default CLI configuration file. [GH-24728]
|
* cli: When using the `TF_CLI_CONFIG_FILE` environment variable to override where Terraform looks for CLI configuration, Terraform will now ignore the default CLI configuration directory as well as the default CLI configuration file. [GH-24728]
|
||||||
* cli: The `terraform login` command in OAuth2 mode now implements the PKCE OAuth 2 extension more correctly. Previously it was not compliant with all of the details of the specification. [GH-24858]
|
* cli: The `terraform login` command in OAuth2 mode now implements the PKCE OAuth 2 extension more correctly. Previously it was not compliant with all of the details of the specification. [GH-24858]
|
||||||
|
* command: Fix panic for nil credentials source, which can be caused by an unset HOME environment variable [GH-25110]
|
||||||
* command/fmt: Include source snippets in errors [GH-24471]
|
* command/fmt: Include source snippets in errors [GH-24471]
|
||||||
* command/format: Fix diagnostic output to show multi-line code snippets correctly [GH-24473]
|
* command/format: Fix diagnostic output to show multi-line code snippets correctly [GH-24473]
|
||||||
* command/show (json output): fix inconsistency in resource addresses between plan and prior state output [GH-24256]
|
* command/show (json output): fix inconsistency in resource addresses between plan and prior state output [GH-24256]
|
||||||
|
@ -65,6 +66,7 @@ BUG FIXES:
|
||||||
* lang: Fix non-string key panics in map function [GH-24277]
|
* lang: Fix non-string key panics in map function [GH-24277]
|
||||||
* lang: `substr("abc", 0, 0)` would previously return `"abc"`, despite the length argument being `0`. This has been changed to return an empty string when length is zero. [GH-24318]
|
* lang: `substr("abc", 0, 0)` would previously return `"abc"`, despite the length argument being `0`. This has been changed to return an empty string when length is zero. [GH-24318]
|
||||||
* lang: `ceil(1/0)` and `floor(1/0)` would previously return a large integer value, rather than infinity. This has been fixed. [GH-21463]
|
* lang: `ceil(1/0)` and `floor(1/0)` would previously return a large integer value, rather than infinity. This has been fixed. [GH-21463]
|
||||||
|
* lang: Add support for OpenSSH RSA key format to `rsadecrypt` function [GH-25112]
|
||||||
* provisioner/chef: Gracefully handle non-failure (RFC062) exit codes [GH-19155]
|
* provisioner/chef: Gracefully handle non-failure (RFC062) exit codes [GH-19155]
|
||||||
* provisioner/habitat: Fix permissions on user.toml [GH-24321]
|
* provisioner/habitat: Fix permissions on user.toml [GH-24321]
|
||||||
* provider/terraform: The `terraform_remote_state` data source will no longer attempt to "configure" the selected backend during validation, which means backends will not try to perform remote actions such as verifying credentials during `terraform validate`. Local validation still applies in all cases, and the configuration step will still occur prior to actually reading the remote state in a normal plan/apply operation. [GH-24887]
|
* provider/terraform: The `terraform_remote_state` data source will no longer attempt to "configure" the selected backend during validation, which means backends will not try to perform remote actions such as verifying credentials during `terraform validate`. Local validation still applies in all cases, and the configuration step will still occur prior to actually reading the remote state in a normal plan/apply operation. [GH-24887]
|
||||||
|
|
Loading…
Reference in New Issue