v1.11.0-rc1
📦 terraformView on GitHub →
✨ 8 features🐛 3 fixes⚡ 1 deprecations🔧 8 symbols
Summary
Terraform 1.11.0-rc1 introduces native S3 state locking, write-only resource attributes, and promotes JUnit XML test reporting to general availability.
Migration Steps
- To adopt native S3 state locking, add 'use_lockfile = true' to your S3 backend configuration and migrate away from DynamoDB locking arguments.
✨ New Features
- Added write-only attributes to resources which are not persisted in state and support ephemeral values.
- The '-junit-xml' option for 'terraform test' is now generally available for creating test reports.
- S3 native state locking is now generally available via the 'use_lockfile' argument.
- New 'terraform modules -json' command to list installed modules and their reference status.
- Added 'override_during' attribute to 'terraform test' to support mocked values during plan phases.
- Added 'state_key' attribute for 'run' blocks in 'terraform test' for internal state file control.
- Provider installation now supports .netrc credentials for registry downloads.
- Official Docker image now includes the 'ca-certificates' package.
🐛 Bug Fixes
- Corrected error message when ephemeral values are included in provisioner output.
- Changed misleading error to a warning when attempting to override a variable during apply via TF_VAR_ environment variables.
- Fixed a crash in backends when interrupting during an interactive prompt.
🔧 Affected Symbols
terraform testterraform modulesbackend.s3use_lockfileoverride_duringstate_key-junit-xmlTF_VAR_⚡ Deprecations
- DynamoDB-related arguments for S3 state locking are deprecated in favor of the new S3 native locking mechanism (use_lockfile).