terraform output: Now supports a new "raw" mode, activated by the -raw option, for printing out the raw string representation of a particular output value. (#27212)
Only primitive-typed values have a string representation, so this formatting mode is not compatible with complex types. The -json mode is still available as a general way to get a machine-readable representation of an output value of any type.
config: for_each now allows maps whose element values are sensitive, as long as the element keys and the map itself are not sensitive. (#27247)
BUG FIXES:
config: Fix anytrue and alltrue functions when called with values which are not known until apply. (#27240)
config: Fix sum function when called with values which are not known until apply. Also allows sum to cope with numbers too large to represent in float64, along with correctly handling errors around infinite values. (#27249)
config: Fixed panic when referencing sensitive values in resource count expressions (#27238)
config: Fix incorrect attributes in diagnostics when validating objects (#27010)
core: Prevent unexpected updates during plan when multiple sensitive values are involved (#27318)
dependencies: Fix several small bugs related to the use of sensitive values with expressions and functions.
lang: Fix panic when calling coalescelist with a null argument (#26988)
terraform apply: -refresh=false was skipped when running apply directly (#27233)
terraform init: setting -get-plugins to false will now cause a warning, as this flag has been a no-op since 0.13.0 and usage is better served through using provider_installation blocks (#27092)
terraform init and other commands which interact with the dependency lock file: These will now generate a normal error message if the lock file is incorrectly a directory, rather than crashing as before. (#27250)
v0.14.2
0.14.2 (December 08, 2020)
BUG FIXES:
backend/remote: Disable the remote backend version compatibility check for workspaces set to use the "latest" pseudo-version. (#27199)
providers/terraform: Disable the remote backend version compatibility check for the terraform_remote_state data source. This check is unnecessary, because the data source is read-only by definition. (#27197)
v0.14.1
0.14.1 (December 08, 2020)
ENHANCEMENTS:
backend/remote: When using the enhanced remote backend with commands which locally modify state, verify that the local Terraform version and the configured remote workspace Terraform version are compatible. This prevents accidentally upgrading the remote state to an incompatible version. The check is skipped for commands which do not write state, and can also be disabled by the use of a new command-line flag, -ignore-remote-version. (#26947)
BUG FIXES:
configs: Fix for errors when using multiple layers of sensitive input variables (#27095)
configs: Fix error when using sensitive input variables in conditionals (#27107)
core: Fix permanent diff when a resource changes only in sensitivity, for example due to changing the sensitivity of a variable or output used as an attribute value. (#27128)
core: Fix issues where ignore_changes appears to not work, or causes validation errors with some resources. (#27141)
terraform fmt: Fix incorrect formatting with attribute expressions enclosed in parentheses. (#27040)
terraform output: Now supports a new "raw" mode, activated by the -raw option, for printing out the raw string representation of a particular output value. (#27212)
Only primitive-typed values have a string representation, so this formatting mode is not compatible with complex types. The -json mode is still available as a general way to get a machine-readable representation of an output value of any type.
config: for_each now allows maps whose element values are sensitive, as long as the element keys and the map itself are not sensitive. (#27247)
BUG FIXES:
config: Fix anytrue and alltrue functions when called with values which are not known until apply. (#27240)
config: Fix sum function when called with values which are not known until apply. Also allows sum to cope with numbers too large to represent in float64, along with correctly handling errors around infinite values. (#27249)
config: Fixed panic when referencing sensitive values in resource count expressions (#27238)
config: Fix incorrect attributes in diagnostics when validating objects (#27010)
core: Prevent unexpected updates during plan when multiple sensitive values are involved (#27318)
dependencies: Fix several small bugs related to the use of sensitive values with expressions and functions.
lang: Fix panic when calling coalescelist with a null argument (#26988)
terraform apply: -refresh=false was skipped when running apply directly (#27233)
terraform init: setting -get-plugins to false will now cause a warning, as this flag has been a no-op since 0.13.0 and usage is better served through using provider_installation blocks (#27092)
terraform init and other commands which interact with the dependency lock file: These will now generate a normal error message if the lock file is incorrectly a directory, rather than crashing as before. (#27250)
0.14.2 (December 08, 2020)
BUG FIXES:
backend/remote: Disable the remote backend version compatibility check for workspaces set to use the "latest" pseudo-version. (#27199)
providers/terraform: Disable the remote backend version compatibility check for the terraform_remote_state data source. This check is unnecessary, because the data source is read-only by definition. (#27197)
0.14.1 (December 08, 2020)
ENHANCEMENTS:
backend/remote: When using the enhanced remote backend with commands which locally modify state, verify that the local Terraform version and the configured remote workspace Terraform version are compatible. This prevents accidentally upgrading the remote state to an incompatible version. The check is skipped for commands which do not write state, and can also be disabled by the use of a new command-line flag, -ignore-remote-version. (#26947)
BUG FIXES:
configs: Fix for errors when using multiple layers of sensitive input variables (#27095)
configs: Fix error when using sensitive input variables in conditionals (#27107)
core: Fix permanent diff when a resource changes only in sensitivity, for example due to changing the sensitivity of a variable or output used as an attribute value. (#27128)
core: Fix issues where ignore_changes appears to not work, or causes validation errors with some resources. (#27141)
terraform fmt: Fix incorrect formatting with attribute expressions enclosed in parentheses. (#27040)
0.14.0 (December 02, 2020)
NEW FEATURES:
Terraform now supports marking input variables as sensitive, and will propagate that sensitivity through expressions that derive from sensitive input variables.
terraform init will now generate a lock file in the configuration directory which you can check in to your version control so that Terraform can make the same version selections in future. (#26524)
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
- `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language
- `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language
- `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language
- `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language
- `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme
Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com):
- Update frequency (including time of day and day of week)
- Pull request limits (per update run and/or open at any time)
- Automerge options (never/patch/minor, and dev/runtime dependencies)
- Out-of-range updates (receive only lockfile updates, if desired)
- Security updates (receive only security updates, if desired)
Bumps github.com/hashicorp/terraform from 0.13.2 to 0.14.3.
Release notes
Sourced from github.com/hashicorp/terraform's releases.
Changelog
Sourced from github.com/hashicorp/terraform's changelog.
Commits
f1be491Release v0.14.31995dbdMerge pull request #27325 from hashicorp/backport/dec20_link_updates/jointly-...4ff7c0bbackport of commit 4b56c11f95798486a08a858e6c3441423e2aea7239a1e0bUpdate CHANGELOG.md50311baMerge pull request #27322 from hashicorp/alisdair/update-deps-014efd4ecfgo get github.com/zclconf/go-cty@v1.7.14be25d8update CHANGELOG.md352e146go get github.com/hashicorp/hcl/v2@v2.8.156370adMerge pull request #27321 from hashicorp/jbardin/path-marks-v0.14d20119fplan context test for mysterious changesDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Pull request limits (per update run and/or open at any time) - Automerge options (never/patch/minor, and dev/runtime dependencies) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired)