Why remote_state by default creates s3 bucket?

[pepsi1k]

I don't understand the reason for automatically creating an S3 bucket. What if you made a typo? Would it try to deploy the infrastructure again?

By default, Terraform's S3 backend complains if the bucket doesn't exist, but Terragrunt creates it. I want to use Terragrunt's remote state to pass some variables into it, like so:

remote_state {
  backend = "s3"
  config = {
    aws_profile    = local.aws_profile
    bucket         = "some-bucket-name"
    key            = "${path_relative_to_include()}/terraform.tfstate"
    region         = "eu-central-1"
    encrypt        = true
  }
}

But because of this default behavior, I simply can't, and I have to use some ugly workarounds like:

generate "backend" {
  path      = "backend.tf"
  if_exists = "overwrite_terragrunt"
  contents = templatefile("backend.tftpl", {
    aws_profile = local.aws_profile
    region      = "eu-north-1"
    bucket      = "some-bucket-name"
    key         = "terraform.tfstate"
    encrypt     = true
  })
}

I think the best practice would be to have an option in remote_state like create_bucket = true/false, with the default valuefalse.

[yhakbar]

We're actively changing this. Read the following:
#3445