3

I think a key difference between Terraform Modules and Workspaces is that modules can be inherited and used by other modules and configurations. Terraform Workspaces are intended to be a collection of configurations that represent a single environment, whereas Modules are components that can be utilized by one or more modules/configurations. I think you ...


2

Terraform modules are a way to encapsulate reusable business logic in order to be DRY. For example, you might use a module to define a jenkins setup, then invoke that module every time you want a jenkins server. In other words, you can instantiate modules as many times as you need them to achieve the same outcome. On the other hand, Terraform workspaces ...


1

You might be able to do something with the local-exec Provisioner to push the information out to an external script or file which you could monitor separately during the run. The issue you might encounter is the run order, HCL isn't processed top to bottom like a "traditional" programming language, it works out a dependency tree for the resources ...


1

You can use the Terraform Cloud provider to manage workspace configuration in Terraform Cloud in the same way as you might manage any other infrastructure objects with Terraform. For historical reasons the provider is named tfe, but it can be used to manage both Terraform Enterprise and Terraform Cloud. In particular, you can use the tfe_variable resource ...


1

I think you could achieve something similar by first running Terraform against your RDS resources, and then running Terraform again on all resources. On your first pass, you can use -target option to target only a subset of the resources. (ie. RDS resources). Be aware that using this option is not recommended in Terraform docs. If I were you, I would use ...


Only top voted, non community-wiki answers of a minimum length are eligible