#terraform - August 2024

@ Team, I am interested in learning Terraform and would appreciate it if anyone could advise me on the best way to learn quickly, as I am an expert in cloud technology but not an IaC (Terraform, etc.).

Hi, i hope this is the place to ask such questions;
im trying to upgrade our msk version. we've installed msk using https://github.com/cloudposse/terraform-aws-msk-apache-kafka-cluster (we're still on version 1.4.0)
im running into this error

Error: error deleting MSK Configuration XXX: BadRequestException: Configuration is in use by one or more clusters. Dissociate the configuration from the clusters.

im not sure how to overcome this when using the cloudposse module? can i provide it with the configuration from an external msk configuration resource? i didnt seem to find such an input.

has anyone faced such an issue and can help? thanks!

👋 Hello, team!
I hope this thread is right for the issues.
I take the following error when I try to deploy https://github.com/cloudposse/terraform-aws-rds-cluster/tree/main/examples/complete

╷
│ Error: Unsupported argument
│ 
│   on main.tf line 97, in module "rds_cluster":
│   97:   context = module.this.context
│ 
│ An argument named "context" is not expected here.

I use the same variables in the example, so what could be the issue here?

Hi, I'm trying to autoscale ecs services. I've used the ecs_cloudwatch_autoscale module plus the ecs-cloudwatch-sns-alarms module but the alarm module only accept ARNs for the actions. Is it correct to pass the autoscale policy arns to the actions?

v1.9.4
1.9.4 (August 7, 2024)
BUG FIXES:

core: Unneeded variable validations were being executed during a destroy plan, which could cause plans starting with incomplete state to fail. (#35511)
init: Don't crash when discovering invalid syntax in duplicate required_providers blocks. (<a...

v1.10.0-alpha20240807
1.10.0-alpha20240807 (August 7, 2024)
BUG FIXES:

The error message for an invalid default value for an input variable now indicates when the problem is with a nested value in a complex data type. [<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="2412199978" data-permission-text="Title is private" data-url="https://github.com/hashicorp/terraform/issues/35465" data-hovercard-type="pull_request" data-hovercard-url="/hashicorp/terraform/pull/35465/hovercard"...

Hi! Any way to create a lambda layer with a CloudPosse module?

hi! new here, still reading and learning. out of curiosity: why in versions.tf file for say VPC only greater-than limit is specified for terraform/provider? normally, in semver major version can include breaking changes in API.

Hey everyone, I just published this VSCode extension for more reliable Terraform/OpenTofu code modifications, still in alpha but it's much more accurate than GitHub Copilot and Claude 3.5 because it makes use of the latest provider docs + structured generation make sure the TF code is 100% syntactically valid

I'm not sure how useful this extension is, so I'd love to hear your thoughts

https://youtu.be/Uxk1hsSs6tI?si=PO4xxf9WTODM3fMF

Thats Great @George Fahmy 🎉

Does anyone use the tool tfschema in your Terraform workflows? I was looking into tooling similar to TFlint that gives me greater visibility into desired configuration parameters and found it. Curious if anyone had any cool use cases or integrations

❯ tfschema resource show google_compute_instance
+---------------------------+--------------------------------+----------+----------+----------+-----------+
| ATTRIBUTE                 | TYPE                           | REQUIRED | OPTIONAL | COMPUTED | SENSITIVE |
+---------------------------+--------------------------------+----------+----------+----------+-----------+
| allow_stopping_for_update | bool                           | false    | true     | false    | false     |
| can_ip_forward            | bool                           | false    | true     | false    | false     |
| cpu_platform              | string                         | false    | false    | true     | false     |
| current_status            | string                         | false    | false    | true     | false     |
| deletion_protection       | bool                           | false    | true     | false    | false     |
| description               | string                         | false    | true     | false    | false     |
| desired_status            | string                         | false    | true     | false    | false     |
| effective_labels          | map(string)                    | false    | false    | true     | false     |
| enable_display            | bool                           | false    | true     | false    | false     |
| guest_accelerator         | list(object({ count=number,    | false    | true     | true     | false     |
|                           | type=string }))                |          |          |          |           |
| hostname                  | string                         | false    | true     | false    | false     |
| id                        | string                         | false    | true     | true     | false     |
| instance_id               | string                         | false    | false    | true     | false     |
| label_fingerprint         | string                         | false    | false    | true     | false     |
| labels                    | map(string)                    | false    | true     | false    | false     |
| machine_type              | string                         | true     | false    | false    | false     |
| metadata                  | map(string)                    | false    | true     | false    | false     |
| metadata_fingerprint      | string                         | false    | false    | true     | false     |
| metadata_startup_script   | string                         | false    | true     | false    | false     |
| min_cpu_platform          | string                         | false    | true     | true     | false     |
| name                      | string                         | true     | false    | false    | false     |
| project                   | string                         | false    | true     | true     | false     |
| resource_policies         | list(string)                   | false    | true     | false    | false     |
| self_link                 | string                         | false    | false    | true     | false     |
| tags                      | set(string)                    | false    | true     | false    | false     |
| tags_fingerprint          | string                         | false    | false    | true     | false     |
| terraform_labels          | map(string)                    | false    | false    | true     | false     |
| zone                      | string                         | false    | true     | true     | false     |
+---------------------------+--------------------------------+----------+----------+----------+-----------+

hi, I'm playing around with Atmos and I wonder: would that be considered the best practice to not include *.tfvars / *.tfvars.json files in repository as these are managed and created on the fly by Atmos anyway? for auto generated backend.tf.json I could ask similar question.

v1.10.0-alpha20240814
1.10.0-alpha20240814 (August 14, 2024)
BUG FIXES:

The error message for an invalid default value for an input variable now indicates when the problem is with a nested value in a complex data type. (#35465)
Sensitive marks could be incorrectly transferred to nested resource values, causing erroneous changes during a plan (<a...

👋 Hello, team!
so i am trying to automate (IAC) our glue services
iam-role, s3, Glue Job, Workflow
i am facing this error when i use

terraform {
    source = "tfr:///cloudposse/s3-bucket/aws?version=2.0.3"
}

to import s3 module
or importing iam-role module

terraform {
    source = "tfr:///cloudposse/iam-role/aws?version=0.19.0"
}

Error is

'.terraform\modules\s3_user.s3_user'...
│ fatal: '$GIT_DIR' too big

i tried everything possible increased buffer size, downloaded the module manualy and point the source to my local but still no use
any help please

v1.9.5
1.9.5 (August 20, 2024)
ENHANCEMENTS:

cloud: The cloud block can now interact with workspaces that have HCP resource IDs. (#35495)

BUG FIXES:

core: removed blocks with provisioners were not executed when the resource was in a nested module. (<a href="https://github.com/hashicorp/terraform/issues/35611"...

was wondering if you guys can point me int the right direction... Trying to find a terraform module for aws personalize service. Doesn't seem like the terraform aws provider has a resource for personalize.... unless im not looking in the correct location.... didn't find any from cloudposse either. any recommendation will be appreciated

Just came across this opinionated article on “one root module to rule them all”: https://medium.com/@maximonyshchenko/the-secret-to-terraform-efficiency-a76140a5dfa1

hey! new to atmos, trying it out for the first time
I'm getting the following error trying to convert a repo to use atmos

Could not find the component 'aws-to-github' in the stack 'dev'.
Check that all the context variables are correctly defined in the stack manifests.
Are the component and stack names correct? Did you forget an import?

the directory structure

.
├── atmos.yaml
└── components
    ├── stacks
    │   ├── catalog
    │   │   └── aws-to-github.yaml
    │   ├── deploy
    │   │   ├── _defaults.yaml
    │   │   └── dev.yaml
    │   └── mixins
    │       └── module
    │           ├── aws-to-github.yaml
    │           ├── google-workspace-to-aws.yaml
    │           └── infra-shared.yaml
    └── terraform
        └── aws
            ├── aws-to-github
            │   ├── data.tf
            │   ├── locals.tf
            │   ├── main.tf
            │   ├── policies.tftpl
            │   ├── trust-document.tftpl
            │   └── variables.tf
            └── identity-center
                ├── main.tf
                └── variables.tf

atmos.yaml

base_path: "./"

components:
  terraform:
    base_path: "components/terraform/aws"
    apply_auto_approve: false
    deploy_run_init: true
    init_run_reconfigure: true
    auto_generate_backend_file: false

stacks:
  base_path: "components/stacks"
  included_paths:
    - "deploy/**/*"
  excluded_paths:
    - "deploy/*/_defaults.yaml"
  name_pattern: "{{.vars.env}}-{{.vars.region}}"

logs:
  file: "/dev/stderr"
  level: Info

I'm sure I'm missing something obvious - any ideas?

Hi, at work we use CF and are planning to use TF soon as changes are happening at work.
(I couldn't find here folks asking about learning about TF from scratch). What are some resources that you would suggest to look into in order to learn TF? (other than Hashicorp docs and youtube videos?), I know there are resources out there but I've ran into some that are outdated (uploads of 5yrs etc).
Any suggestions would help! Thank you!
Also, if there are paid ones, I would consider this too.

hey, I was playing with VPC component from terraform-aws-components repo yesterday. it looks that account-map is prerequisite for it. account-map on the other hand needs account component. is there some workaround needed to use just VPC component without account-map?

hi, every time when we plan and apply the terraform script, the elastic beanstalk resource got tainted due to which the elastic beanstalk resource got replaced every time. can anyone please tell how to resolve this problem.

v1.10.0-alpha20240828
1.10.0-alpha20240828 (Aug 28, 2024)
BUG FIXES:

The error message for an invalid default value for an input variable now indicates when the problem is with a nested value in a complex data type. (#35465)
Sensitive marks could be incorrectly transferred to nested resource values, causing erroneous changes during a plan (<a...

Hi Team,

I am trying to delete eks components using the destroy command
and getting this error
│ Error: Unsupported attribute
│
│ on providers.tf line 5, in provider "aws":
│ 5: profile = module.iam_roles.terraform_profile_name
│ ├────────────────
│ │ module.iam_roles is object with 13 attributes
│
│ This object does not have an attribute named "terraform_profile_name".
╵
Releasing state lock. This may take a few moments...

This module is under account map and is being used in provider.tf files<
Can somebody help me in understanding why this is creating an issue during destruction was not an issue during creation, a version issue ?

Hello, I have a few questions around the EKS node group module. I want to create another node group (My last node group is pinned to version 0.27.1! - trying to use v3.1.0 now).
I'm trying to use an existing launch template that we have so I set launch_template_id and ami_type to CUSTOM but i'm getting an error "InvalidParameterException: You cannot specify a kubernetes version to use when specifying an image id to use within the launch template."

I also haven't been able to figure out how to provide a node group name to the module.. it seems to use random_pets to name the new node group.

Hi,
Anyone using latest 'cloudposse/terraform-aws-eks-node-group' for windows nodes plz? I am having issue when node tries to connect to EKS cluster.