![]() ![]() The Terraform configuration is maintained in a Git repository. ![]() The table below summarizes the impact of various combinations. In general, it is not recommended to use feature branches for deployments in the default workspace. While workspaces completely depend upon the state file maintained in the remote backend by Terraform. Git branches maintain various versioned copies of the same configuration that are used to develop new features or Terraform modules. You shouldn’t confuse branches in the version control systems with Terraform workspaces. aws_instance.my_vm: Creation complete after 32 s Apply complete! Resources: 1 added, 0 changed, 0 destroyed. So if you run "terraform plan" Terraform will not see any existing stateĭo you want to perform these actions in workspace "test" ?Īws_instance.my_vm: Still creating. ![]() aws_instance.my_vm: Creation complete after 31 s Apply complete! Resources: 1 added, 0 changed, 0 destroyed. Terraform will perform the actions described above.Īws_instance.my_vm: Still creating. Plan: 1 to add, 0 to change, 0 to destroy. It is a very handy tool that lets us test configurations by giving us flexibility in resource allocation, regional deployments, multi-account deployments, and so on. Workspaces enable us to manage multiple deployments of the same configuration. In this post, we will cover another interesting feature of Terraform – Workspaces.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |