Infrastructure as Code: Terraform 1.1 eröffnet native Cloud-Integration

Share your love

Half a year after HashiCorp presented the first milestone of its Infrastructure-as-Code platform, the first minor release is now following with Terraform 1.1. In addition to the full native integration into the Terraform Cloud, the update has, among other things, some new features for refactoring in modules.

Developers who wanted to connect Terraform to the cloud previously had to set up a remote resource. From version 1.1 there is the option to set a cloud-Block to be added, which then also allows the use of the CLI. In this way, not only can input variables be transferred to the Terraform Cloud, but all CLI-based workflows can also be simplified. With the flag -var For example, variables can be marked for a single run.

Workspace management should also be made easier thanks to dedicated workspace tags, for example when it comes to mapping Terraform Cloud Workspaces to the current configuration. The native integration also promises more meaningful error messages.

After the upgrade of a module required in connection with the migration of objects, developers always had to issue the command terraform state mv run manually. The newly introduced in Terraform 1.1 move-Blocks now open up the possibility when refactoring in modules to record in the source code of the module when the address of a resource or resource instance has changed. As a result, Terraform is able to automatically migrate the existing objects to the new addresses during the planning phase. This applies at least to all cases in which the change can be expressed as a static configuration. For more complex scenarios that are not suitable for a declarative configuration, developers can continue to use terraform state mv To fall back on.

Read Also   Texas Instruments: Construction of new semiconductor factories begins later despite lack of chips

Whenever Terraform suggests deleting certain resource instances, the terraform plan as well as terraform apply additional notes explaining why Terraform proposed this action. For example, do users reduce the counter reading in the count-Argument of a resource, Terraform will cite this as a justification when it proposes to delete all existing objects with a higher count.

Terraform 1.1 is available now. A complete overview of all new features and bug fixes, including information on upgrading from the previous version can be found in the changelog on GitHub. There binaries for common operating systems are also available for download under the Mozilla Public License v2.0.


(map)

Article Source

Share your love