1.1.0 (Unreleased)
UPGRADE NOTES:
-
Terraform on macOS now requires macOS 10.13 High Sierra or later; Older macOS versions are no longer supported.
-
The
terraform graph
command no longer supports-type=validate
and-type=eval
options. The validate graph is always the same as the plan graph anyway, and the "eval" graph was just an implementation detail of theterraform console
command. The default behavior of creating a plan graph should be a reasonable replacement for both of the removed graph modes. (Please note thatterraform graph
is not covered by the Terraform v1.0 compatibility promises, because its behavior inherently exposes Terraform Core implementation details, so we recommend it only for interactive debugging tasks and not for use in automation.) -
terraform apply
with a previously-saved plan file will now verify that the provider plugin packages used to create the plan fully match the ones used during apply, using the same checksum scheme that Terraform normally uses for the dependency lock file. Previously Terraform was checking consistency of plugins from a plan file using a legacy mechanism which covered only the main plugin executable, not any other files that might be distributed alongside in the plugin package.This additional check should not affect typical plugins that conform to the expectation that a plugin package's contents are immutable once released, but may affect a hypothetical in-house plugin that intentionally modifies extra files in its package directory somehow between plan and apply. If you have such a plugin, you'll need to change its approach to store those files in some other location separate from the package directory. This is a minor compatibility break motivated by increasing the assurance that plugins have not been inadvertently or maliciously modified between plan and apply.
NEW FEATURES:
-
moved
blocks for refactoring within modules: Module authors can now record in module source code whenever they've changed the address of a resource or resource instance, and then during planning Terraform will automatically migrate existing objects in the state to new addresses.This therefore avoids the need for module users to manually run
terraform state mv
after upgrading to a newer module version, as long as the change is expressible as static configuration. However,terraform state mv
remains available for use in more complex migration situations that are not well-suited to declarative configuration. -
A new
cloud
option in theterraform
settings block adds a more native integration for Terraform Cloud and its CLI-driven run workflow. The Cloud integration includes several enhancements, including per-run variable support using the-var
flag, the ability to map Terraform Cloud workspaces to the current configuration via Workspace Tags, and an improved user experience for Terraform Cloud/Enterprise users with actionable error messages and prompts. (#29826) -
terraform plan
andterraform apply
: When Terraform plans to destroy a resource instance due to it no longer being declared in the configuration, the proposed plan output will now include a note hinting at what situation prompted that proposal, so you can more easily see what configuration change might avoid the object being destroyed. (#29637) -
terraform plan
andterraform apply
: When Terraform automatically moves a singleton resource instance to index zero or vice-versa in response to adding or removingcount
, it'll report explicitly that it did so as part of the plan output. (#29605) -
config: a new
type()
function, available only interraform console
. (#28501)
ENHANCEMENTS:
- config: Terraform now checks the syntax of and normalizes module source addresses (the
source
argument inmodule
blocks) during configuration decoding rather than only at module installation time. This is largely just an internal refactoring, but a visible benefit of this change is that theterraform init
messages about module downloading will now show the canonical module package address Terraform is downloading from, after interpreting the special shorthands for common cases like GitHub URLs. (#28854) - config: A new variable attribute
nullable
, which defines whether a variable can be null within a module. Settingnullable
tofalse
ensures that a variable value will not benull
, and that a non-null default is used whennull
is given as a module argument (#29832) terraform plan
andterraform apply
: Terraform will now report explicitly in the UI if it automatically moves a resource instance to a new address as a result of adding or removing thecount
argument from an existing resource. For example, if you previously hadresource "aws_subnet" "example"
withoutcount
, you might haveaws_subnet.example
already bound to a remote object in your state. If you addcount = 1
to that resource then Terraform would previously silently rebind the object toaws_subnet.example[0]
as part of planning, whereas now Terraform will mention that it did so explicitly in the plan description. (#29605)terraform workspace delete
: will now allow deleting a workspace whose state contains only data resource instances and output values, without runningterraform destroy
first. Previously the presence of data resources would require using-force
to override the safety check guarding against accidentally forgetting about remote objects, but a data resource is not responsible for the management of its associated remote object(s) anyway. (#29754)- provisioner/remote-exec and provisioner/file: When using SSH agent authentication mode on Windows, Terraform can now detect and use the Windows 10 built-in OpenSSH Client's SSH Agent, when available, in addition to the existing support for the third-party solution Pageant that was already supported. (#29747)
BUG FIXES:
- backend/oss: Flatten
assume_role
block attributes, so that they may be more easily represented in a compatible way withterraform_remote_state
(#29307) - config: Fixed a bug in which
ignore_changes = all
would not work in override files (#29849) - core: Use more precise typing information of resources during config validation (#29862)
- core: Fixed an issue where provider configuration input variables were not properly merging with values in configuration (#29000)
- core: Reduce scope of dependencies that may defer reading of data sources when using
depends_on
or directly referencing managed resources (#29682) - cli: Blocks using SchemaConfigModeAttr in the provider SDK can now represented in the plan json output (#29522)
- cli: Prevent applying a stale planfile when there was no previous state (#29755)
- cli: Improve list nested attribute rendering (#29827)
- command: Fixed an issue where the backend cache hash value was being updated too early in backend initialization/migrate flows, causing situations where
init
would not properly restart a backend migration process if that process failed previously. (#29860)