Hi Bryan,

Thanks for asking this. It seems you have great knowledge of Terraform.
So, when you run terraform cloud remotely like using vcs providers, there is no need to configure terraform block with cloud block.
You can see my code which is mentioned as main.tf, that does not contain terraform block. Terraform block is needed if you run your code from your local like Terraform Cli and you want to connect with Terraform Cloud.

The below terraform block is for run terraform from CLI to Terraform Cloud.

terraform {
cloud {
organization = “my-org”
hostname = “app.terraform.io”

workspaces {
tags = [“dev”, “prod”]
# name = “dev”
}
}
}

This is the terraform block with cloud block configurations. And inside the workspace block, I have 2 arguments. We can only use one of the arguments either ‘name’ or ‘dev’.
If you want to use your terraform code in a single workspace then you can use the ‘name’ argument. Otherwise, you can use ‘tags’ to mention multiple workspaces.
As you mentioned in your reply, if your code has ‘name’ = ‘dev’, then it only runs in the dev workspace.

I think I am fulfilled with your question. If you need more clarification, any time you can ask me. I am ready to help you.
And I am pretty sure I will create a blog about terraform backend types. That will help you to get a better understanding of the terraform block.

Thanks,
Jerin

I enjoyed your article on terraform cloud and deploying to multiple environments. I used this article as a guide for setting up a couple environments that we have. I have a question for you which may have not ran across before if you have time. 🙂

In our case we have a dev environment and prod environment as described in your article. We have used a different variable set for each workspace for the purposes of account and credential information. This seems to work fine.

What I don’t understand with Terraform Cloud and can’t find any documentation around is how the terraform block works with different workspaces. I’m specifically talking about the workspaces block within the cloud block. Is this ignored during run if it’s ran via remote?

Using your example, I am assuming at the top of you main.tf file you have something that looks like this:

terraform {
required_version = “>= 1.1.1”

cloud {
organization = “xyz_org”
workspaces {
name = “dev”
}
}
}

If you are using the same main.tf file in both your dev and prod workspaces and your main.tf file has the workspace defined as dev. I am guessing this is ignored when a run executes in your prod workspace. Is that true? That seems to be what I am seeing.

Thanks writing for the article and the response in advance!

Also it is very very basic and not useful in realtime

Do you have an article that runs a java application i.e. nohup java -jar ***** from startup script?

It is every hour of every day. You can contact us at https://www.easydeploy.cloud/contact-us if you have further query.

For now, it is only available for Aurora MySQL and Aurora PostgreSQL.

Yes, AWS has announced steps for PostgreSQL but you need to choose Aurora PostgreSQL serverless to have autoscaling enabled.