#terraform-aws-modules (2023-06)

terraform Terraform Modules

Discussions related to https://github.com/terraform-aws-modules

Archive: https://archive.sweetops.com/terraform-aws-modules/

2023-06-07

Samuel Crudge avatar
Samuel Crudge

Hello!

Is it possible to get the PR in this message looked at as its a blocker on upgrading the Elasticbeanstalk module across over 20 projects. https://sweetops.slack.com/archives/CB6GHNLG0/p1686127285090189

Hello! Is there any Github managers here? Our infra is blocked from upgrading ElasticBeanstalk module to newer modules due to a issue raised. There has been a solution offered but there has been no movement.

is there any chance of getting this looked at?

1
Brent Garber avatar
Brent Garber
1
jose.amengual avatar
jose.amengual

which part?

jose.amengual avatar
jose.amengual

the external ENI?

Brent Garber avatar
Brent Garber

The aws_eip resource

jose.amengual avatar
jose.amengual

the vpc/domain option?

Brent Garber avatar
Brent Garber
#161 Dependency on aws provider >5.0

Describe the Bug

The recent changes to aws_eip force a dependency on the 5.0 aws provider. Using 4.x throws errors with

on .terraform/modules/data_host.box/main.tf line 175, in resource "aws_eip" "default":
  domain   = "vpc"
Can't configure a value for "domain": its value will be decided automatically based on the result of applying this configuration.

Caused by #159, if this is intended behavior, documentation and version requirements should be updated to not say the dependency is against >= 2.0

Expected Behavior

Resources deploy fine

Steps to Reproduce

Try to use module with 4.x aws provider

Screenshots

No response

Environment

No response

Additional Context

No response

jose.amengual avatar
jose.amengual

we could roll that back, but I will defer to @Andriy Knysh (Cloud Posse) when he has some time

Brent Garber avatar
Brent Garber

Doesnt necessarily need rolled back, just [versions.tf](http://versions.tf) updated to track so it’d be more apparent on breaking changes on new releases

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

We are supposed to cutting a new major version for breaking changes by adding the major label to breaking PRs.

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

If this depends on v5 fuctionality, it shouldn’t have been merged before https://github.com/cloudposse/terraform-aws-ec2-instance/pull/160

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

@Max Lobur (Cloud Posse) can you sort this one out?

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

using the major label, we can support v4 and v5 concurrently, since we’ll automatically cut a release branch for the previous release, in this case release/v0

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

@Linda Pham (Cloud Posse) @Gabriela Campana (Cloud Posse)

Andriy Knysh (Cloud Posse) avatar
Andriy Knysh (Cloud Posse)

I missed the fact that one change from @jose.amengual PR works only with the aws provider v5

Andriy Knysh (Cloud Posse) avatar
Andriy Knysh (Cloud Posse)

we need to make the release a pre-release, and cut a new major one with the same code

1
Max Lobur (Cloud Posse) avatar
Max Lobur (Cloud Posse)

correct

Max Lobur (Cloud Posse) avatar
Max Lobur (Cloud Posse)

will do now

1
jose.amengual avatar
jose.amengual

and that fix I added because tflint was complaining in the checks

Max Lobur (Cloud Posse) avatar
Max Lobur (Cloud Posse)

no the breaking fix is the vpc iface change

Max Lobur (Cloud Posse) avatar
Max Lobur (Cloud Posse)

they changed boolean to string

jose.amengual avatar
jose.amengual

the vpc = domain on the eip?

1
Max Lobur (Cloud Posse) avatar
Max Lobur (Cloud Posse)
  1. released 1.0.0
  2. branch relase/v0 auto-created
  3. I will revert the vpc change there now, pin provider to 4, and test
Max Lobur (Cloud Posse) avatar
Max Lobur (Cloud Posse)

let’s merge^

Andriy Knysh (Cloud Posse) avatar
Andriy Knysh (Cloud Posse)

approved and added label minor (if it’s what you wanted to release)

1
Max Lobur (Cloud Posse) avatar
Max Lobur (Cloud Posse)

0.50.0 - supports V4 1.0.0 - supports V5

jose.amengual avatar
jose.amengual

thanks guys and sorry for the mess I made

Max Lobur (Cloud Posse) avatar
Max Lobur (Cloud Posse)

np, I will keep this in mind for other updates too

jose.amengual avatar
jose.amengual

specially if tflint says deprecated or it fails etc since tflint I guess check the latest only

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

@jose.amengual no problem. This is all new, so it will become more common. It’s a good heads up!

1

2023-06-08

Linda Pham (Cloud Posse) avatar
Linda Pham (Cloud Posse)
02:58:40 PM

@Linda Pham (Cloud Posse) has joined the channel

Gabriela Campana (Cloud Posse) avatar
Gabriela Campana (Cloud Posse)
02:58:40 PM

@Gabriela Campana (Cloud Posse) has joined the channel

2023-06-19

Samuel Crudge avatar
Samuel Crudge

Hi there, I can’t find any reference to one but is there a Cloudposse module for Cloudwatch dashboard?

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

No…

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

We’re using mostly datadog

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

(would love to have one though!)

Samuel Crudge avatar
Samuel Crudge

Thanks Erik! i’ve resorted to raw TF and playing with trying to create widgets dynamically based on resource count. if i get it working il submit it for a module for the community

1
Samuel Crudge avatar
Samuel Crudge

i did find a solution to this but it gets complex messing with json objects, looks like you could with some thought make a module around it

    keyboard_arrow_up