#terraform - June 2025 | Slack Archive

Zapier9 months ago

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 Jun 11, 2025 01:30PM.

👉️ Register for Webinar

#office-hours (our channel)

Jan Costandius9 months ago

There are some missing features from the current GuardDuty module that are addressed in this PR. Are there any plans to review it?

rss9 months ago(edited)

v1.13.0-alpha20250604
1.13.0-alpha20250604 (June 04, 2025)
NEW FEATURES:

The new command terraform stacks exposes some stack operations through the cli. The available subcommands depend on the stacks plugin implementation. Use terraform stacks -help to see available commands. (#36931)

ENHANCEMENTS:

Filesystem functions are now checked for consistent...

RB9 months ago

The new aws v6 terraform provider is planning to be released on Jun 16. It’s a major release so it may have breaking changes that could break terraform workflows.

https://registry.terraform.io/providers/hashicorp/aws/latest/docs/guides/version-6-upgrade

Are upstream terraform components planned to be upgraded prior to the release or same time as the release? or would it be better for us to pin to aws v5 locally in components prior to the upgrade?

Zapier9 months ago

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 Jun 18, 2025 01:30PM.

👉️ Register for Webinar

#office-hours (our channel)

Matt B8 months ago

Hey Everyone - We've recently started a channel to provide DevOps Updates. I'd love to get some feedback where possible.

Multi‑env Terraform Stacks: one codebase, dev→stage→prod with auto plan/apply orchestration

https://www.youtube.com/watch?v=0P32gU_PrlM

rss8 months ago(edited)

v1.12.2
1.12.2 (June 11, 2025)
BUG FIXES:

partial ephemeral values were rejected in ephemeral outputs (#37210)

Zapier8 months ago

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 Jun 25, 2025 01:30PM.

👉️ Register for Webinar

#office-hours (our channel)

mika_l8 months ago

Hiya, is https://github.com/cloudposse/terraform-aws-tfstate-backend still updated, and this the right place to ask about it? I have a PR there since january, waiting for review. I do sometimes want to utilize a role 🙂

Michael8 months ago

Anybody else having fun with today's major release for the Helm provider that migrates from the SDKv2 to the Plugin Framework and changes a bunch of blocks to nested objects? We are seeing a bunch of red pipelines
https://github.com/hashicorp/terraform-provider-helm/blob/v3.0.0/docs/guides/v3-upgrade-guide.md

Ivan K8 months ago

Good afternoon, I am new to your Slack, so if my question is in a wrong channel please let me know. I have been using your modules for awhile now and they are great!

This morning I got an error with https://github.com/cloudposse/terraform-aws-ecs-cluster complaining about Blocks of type "elastic_gpu_specifications" are not expected here. I do not reference elastic_gpu_specifications in my code per say but it is pulled in when running plan

Has anyone had this error or have suggestions how to resolve it? It is currently a blocker for me 😞

rss8 months ago(edited)

v1.13.0-alpha20250623
1.13.0-alpha20250623 (June 23, 2025)
NEW FEATURES:

The new command terraform stacks exposes some stack operations through the cli. The available subcommands depend on the stacks plugin implementation. Use terraform stacks -help to see available commands. (#36931)

ENHANCEMENTS:

Filesystem functions are now checked for consistent...

Zapier8 months ago

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 Jul 02, 2025 01:30PM.

👉️ Register for Webinar

#office-hours (our channel)

James Humphries8 months ago

🎉 OpenTofu v1.10.0 has been released 🎉

https://github.com/opentofu/opentofu/releases/tag/v1.10.0
https://opentofu.org/blog/opentofu-1-10-0/

Quixotical8 months ago

hey quick question and sorry if this is answered somewhere else, but if I made a pull request again one of the cloudposse modules to fix a bug, is there anywhere I can go to get some eyes on it to help it move through the review process & give me feedback on it?

andrew_pintxo8 months ago

Hello, I have a question
I have upgraded aws provider to

aws = {
      source  = "hashicorp/aws"
      version = "= 5.87.0"
    }

And than needed to upgrade a version of module too

module "postgres" {
  source  = "cloudposse/rds/aws"
  version = "0.38.7"

After plan or apply - I do have this. As I have understood it wants to update in place something on my rds instance
So the questions are, how safe it is? Why it wants to update password especialy?
Thank you in advance for a help, advise, answer.

 # module.postgres.aws_db_instance.default[0] will be updated in-place
  ~ resource "aws_db_instance" "default" {
      + allow_major_version_upgrade           = false
      + apply_immediately                     = true
      + character_set_name                    = ""
      + custom_iam_instance_profile           = ""
      + domain                                = ""
      + domain_auth_secret_arn                = ""
      + domain_fqdn                           = ""
      + domain_iam_role_name                  = ""
      + domain_ou                             = ""
      + final_snapshot_identifier             = "org-prod-postgres-final-snapshot"
        id                                    = "db-P6THKC24TWHUTNVMOWEYTEJ000"
      + identifier_prefix                     = ""
      + monitoring_role_arn                   = ""
      + nchar_character_set_name              = ""
      + password                              = (sensitive value)
      + replica_mode                          = ""
      + replicate_source_db                   = ""
      ~ skip_final_snapshot                   = true -> false
        tags                                  = {
            "Name"      = "org-prod-postgres"
            "Namespace" = "org"
            "Stage"     = "prod"
        }
      + timezone                              = ""
        # (54 unchanged attributes hidden)

}

gabuto8 months ago

Hello. I have a question for CloudPosse' team about the datadog module. What benefits do I get by using the module instead of managing the monitors as jsons?

Brian8 months ago

Anyone had issues switching to OpenTofu with S3 backend and use_lockfile enabled?

Craig8 months ago(edited)

Hello, I am using the

module "app-security-group" {
  source  = "cloudposse/security-group/aws"
  version = "2.2.0"
...<SNIP>>...
}

module and am trying to import AWS resources that already exist into my state

import {
  to = module.app-security-group.aws_security_group.default[0]
  id = "<my_sg_id>"
}

I've verified my creds & all are working correctly since I don't get an error from the CLI:

 ➜ tofu import -var-file=migration.tfvars 'module.app-security-group.aws_security_group.default[0]' <<MY_SG_ID>>
data.aws_caller_identity.current: Reading...
data.aws_caller_identity.current: Read complete after 0s [id=<<SNIP>>]

Import successful!

The resources that were imported are shown above. These resources

but when I run my plan using the exact same resource naming/structure, I get an error:

│ Error: Configuration for import target does not exist
│ 
│ The configuration for the given import module.app-security-group.aws_security_group.default[0] does not exist. All target instances must have an associated configuration to be imported.

I'm a bit lost here as I've tried like every permutation of the resource name I can think of to get these resources to import, all without any luck.

Craig8 months ago

module "app-security-group" {
  source  = "cloudposse/security-group/aws"
  version = "2.2.0"

  namespace = local.namespace
  name      = "app"

  allow_all_egress = true

  rules = [
    {
      key         = "HTTP"
      type        = "ingress"
      from_port   = 80
      to_port     = 80
      protocol    = "tcp"
      cidr_blocks = ["0.0.0.0/0"]
      self        = null
      description = "Allow HTTP from anywhere"
    }
  ]

  vpc_id = local.vpc_id
}

is what I have in our Terraform

Zapier8 months ago

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 Jul 09, 2025 01:30PM.

👉️ Register for Webinar

#office-hours (our channel)

Michael8 months ago

Random question of the day. I was curious why the eks/platform component was deprecated? I didn't even realize it was until today