#terraform - February 2025

Tired of boring Terraform outputs? Say “I am the danger” to dull pipelines with the Breaking Bad Terraform provider. Inject some Heisenberg wisdom and keep things interesting:

Repo: https://github.com/The-Infra-Company/terraform-provider-breakingbad

Join us for "Office Hours" every Wednesday 01:30PM (PST, GMT-7) via Zoom.

This is an opportunity to ask us questions on terraform and get to know others in the community on a more personal level. Next one is Feb 12, 2025 01:30PM.

👉️ Register for Webinar

#office-hours (our channel)

v1.11.0-beta2
1.11.0-beta2 (February 05, 2025)
NEW FEATURES:


Add write-only attributes to resources. Providers can specify that certain attributes are write-only. They are not persisted in state. You can use ephemeral values in write-only attributes. (#36031)


terraform test: The -junit-xml option for the terraform test command is now...

Hi awesome people!
I’ve been using your great awsutils provider to take care of removing default VPCs, but I need to use it in a region that isn’t currently supported by the version of the AWS Go SDK that you have built with.

I don’t suppose there’s any chance of a new release to fix this is there?

I see there’s a pull request from someone to address this I think.

https://github.com/cloudposse/terraform-provider-awsutils/pull/73

Join us for "Office Hours" every Wednesday 01:30PM (PST, GMT-7) via Zoom.

This is an opportunity to ask us questions on terraform and get to know others in the community on a more personal level. Next one is Feb 19, 2025 01:30PM.

👉️ Register for Webinar

#office-hours (our channel)

Hello. Longtime Ops person here, just getting more into the Terraform world now. (I've been using it for four years but only with homegrown modules.)

We have some DynamoDB tables that were created with Terraform and now we want to:
a) add autoscaling,
b) modularize it, so that all new tables will be created with autoscaling.

I thought, aha! I'll use terraform-aws-modules, but there is a warning that Terraform will recreate the table if you turn on autoscaling, and it does! There is an additional note, "In this case you will need to move the old aws_dynamodb_table resource that is being destroyed to the new resource that is being created" and I don't quite understand it. Why does Terraform recreate the table, and is running the terraform state mv command meant to keep it from recreating the table? I don't want to lose any data.

As an additional meta question, is this an appropriate forum to ask about terraform-aws-modules, or is there a more appropriate place?

v1.11.0-rc1
1.11.0-rc1 (February 12, 2025)
NEW FEATURES:


Add write-only attributes to resources. Providers can specify that certain attributes are write-only. They are not persisted in state. You can use ephemeral values in write-only attributes. (#36031)


terraform test: The -junit-xml option for the terraform test command is now generally...

v1.12.0-alpha20250213
1.12.0-alpha20250213 (February 13, 2025)
EXPERIMENTS:
Experiments are only enabled in alpha releases of Terraform CLI. The following features are not yet available in stable releases.

The new command terraform rpcapi exposes some Terraform Core functionality through an RPC interface compatible with go-plugin. The exact RPC API exposed here is currently subject to change at any time, because it's here primarily as a vehicle to support the...

Join us for "Office Hours" every Wednesday 01:30PM (PST, GMT-7) via Zoom.

This is an opportunity to ask us questions on terraform and get to know others in the community on a more personal level. Next one is Feb 26, 2025 01:30PM.

👉️ Register for Webinar

#office-hours (our channel)

Howdy Folks! I have a quick question regarding this module https://github.com/cloudposse/terraform-aws-code-deploy/. Is there any chance someone could cut a new release for this module? It's had activity over the last few years yet the last tagged release was in 2021. Is this the right channel to ask this?

v1.11.0-rc2
1.11.0-rc2 (February 19, 2025)
NEW FEATURES:


Add write-only attributes to resources. Providers can specify that certain attributes are write-only. They are not persisted in state. You can use ephemeral values in write-only attributes. (#36031)


terraform test: The -junit-xml option for the terraform test command is now generally...

v1.11.0-rc3
1.11.0-rc3 (February 21, 2025)
NEW FEATURES:


Add write-only attributes to resources. Providers can specify that certain attributes are write-only. They are not persisted in state. You can use ephemeral values in write-only attributes. (#36031)


terraform test: The -junit-xml option for the terraform test command is now generally...

Join us for "Office Hours" every Wednesday 01:30PM (PST, GMT-7) via Zoom.

This is an opportunity to ask us questions on terraform and get to know others in the community on a more personal level. Next one is Mar 05, 2025 01:30PM.

👉️ Register for Webinar

#office-hours (our channel)

I wanted to get feedback on two migration strategies for converting a regional Aurora RDS cluster to a Global Database:

1. In-place Conversion:
◦ Convert existing regional cluster to Global Database
◦ Import into a forked version of cloudposse/aws-aurora-postgres component, which implements a aws_rds_global_cluster setup
◦ This could work well, but not sure how easy it's going to be to jam the Global RDS Dataset cluster into a fork of the regional cluster component.
2. Snapshot & Restore:
◦ Create snapshot of regional cluster
◦ Provision new Global Database cluster using my fork of cloudposse/aws-aurora-postgres component.
◦ Restore from snapshot
◦ This seems less complex and less prone to issues, but has more prod down time.
Has anyone successfully imported an existing Aurora Global Database into the Cloud Posse component? Are there other ways to doing this that I haven't thought of?

v1.11.0
1.11.0 (February 27, 2025)
NEW FEATURES:


Add write-only attributes to resources. Providers can specify that certain attributes are write-only. They are not persisted in state. You can use ephemeral values in write-only attributes. (#36031)


terraform test: The -junit-xml option for the terraform test command is now generally...