#pr-reviews (2024-09)

Pull Request Reviews for Cloud Posse Projects

2024-09-03

Lennart Goedhart avatar
Lennart Goedhart

Small PR to fix a typo in terraform-aws-ecs-cloudwatch-sns-alarms/.

#51 fix: Memory High description typo

Hight -> High

what

Fix typo in alarm description

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

approved and merged, thanks @Lennart Goedhart

#51 fix: Memory High description typo

Hight -> High

what

Fix typo in alarm description

1

2024-09-05

Nitin avatar

PR to enable the dualstack support in the RDS

https://github.com/cloudposse/terraform-aws-rds-cluster/pull/231

#231 Dual stack support

what

why

references

2
1
Gabriela Campana (Cloud Posse) avatar
Gabriela Campana (Cloud Posse)

@Ben Smith (Cloud Posse)

#231 Dual stack support

what

why

references

Nitin avatar

@Ben Smith (Cloud Posse) PR is passed. can you please check now

Gabriela Campana (Cloud Posse) avatar
Gabriela Campana (Cloud Posse)

Merged

2024-09-06

Callum avatar

PR to add the throughput variable for block device tuning on ecs clusters https://github.com/cloudposse/terraform-aws-ecs-cluster/pull/53

#53 feat: add throughput option to block_device_mappings

what

This change adds the through put option to the ebs block_device_mappints object in the capacity_providers_fargate_ec2 variable

why

Support to tune the throughput of the ebs volumes was added to the autoscaling group module in version 0.37.1. As it is not defined in the option block here its not passed through during an execution.

references

Release notes for 0.37.1 of cloudposse/terraform-aws-ec2-autoscale-group

Closes #52

1
Gabriela Campana (Cloud Posse) avatar
Gabriela Campana (Cloud Posse)

@Ben Smith (Cloud Posse)

#53 feat: add throughput option to block_device_mappings

what

This change adds the through put option to the ebs block_device_mappints object in the capacity_providers_fargate_ec2 variable

why

Support to tune the throughput of the ebs volumes was added to the autoscaling group module in version 0.37.1. As it is not defined in the option block here its not passed through during an execution.

references

Release notes for 0.37.1 of cloudposse/terraform-aws-ec2-autoscale-group

Closes #52

Gabriela Campana (Cloud Posse) avatar
Gabriela Campana (Cloud Posse)

@Igor Rodionov

Callum avatar

I guess these got pulled in during the merge from main, I’ve updated them regardless as its a trivial update

Gabriela Campana (Cloud Posse) avatar
Gabriela Campana (Cloud Posse)

@Ben Smith (Cloud Posse) @Igor Rodionov bumping this up

Callum avatar

Is there a step I have missed here? Looks like the terratest has not completed but I am not sure why

Gabriela Campana (Cloud Posse) avatar
Gabriela Campana (Cloud Posse)

Merged. These changes were released in v0.7.0.

Callum avatar

Amazing thanks

np1

2024-09-08

Nitin avatar
#231 Dual stack support

what

RDS cluster can be run in two network modes - IPV4 or DUAL.
Underlying module already supports this parameter

why

It can be mandatory to enable it to be able to connect from ipv6 only runtimes

references

Closes #175

1

2024-09-09

2024-09-10

2024-09-11

Nitin avatar
#245 Allow config endpoint as reader endpoint output

what

This avoids a situation where the reader endpoint tries to use coalesce(null, null, null) when in cluster mode and instead uses the configuration endpoint.

why

When using cluster mode there is no reader endpoint so the output tries to use coalesce(null, null, null) which results in a plan error. As outlined in the AWS docs the config endpoint should be used instead when in cluster mode.

references

Closes #236

1
1
Gabriela Campana (Cloud Posse) avatar
Gabriela Campana (Cloud Posse)

@Ben Smith (Cloud Posse) @Igor Rodionov

#245 Allow config endpoint as reader endpoint output

what

This avoids a situation where the reader endpoint tries to use coalesce(null, null, null) when in cluster mode and instead uses the configuration endpoint.

why

When using cluster mode there is no reader endpoint so the output tries to use coalesce(null, null, null) which results in a plan error. As outlined in the AWS docs the config endpoint should be used instead when in cluster mode.

references

Closes #236

Nitin avatar

Can someone run the terratest again on following PR

Gabriela Campana (Cloud Posse) avatar
Gabriela Campana (Cloud Posse)

@Ben Smith (Cloud Posse) @Igor Rodionov

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

@Igor Rodionov is this due to a missing zone in the new test account maybe?

Gabriela Campana (Cloud Posse) avatar
Gabriela Campana (Cloud Posse)

Nitin, we are chasing this internally and will get back to you asap

Igor Rodionov avatar
Igor Rodionov

@Nitinthat merged. The problem was because we had to update the PR base branch.

2

2024-09-12

2024-09-13

2024-09-14

Nitin avatar
#101 IPv6 communication over VPC peering

what

Allow IPv6 communication b/w VPCs over VPC peering

why

Application hosted in VPC-1 wants to access resources hosted in private subnet of VPC-2 over IPv6.

references

1
Gabriela Campana (Cloud Posse) avatar
Gabriela Campana (Cloud Posse)

@Nitin it seems to be failing Terratest

#101 IPv6 communication over VPC peering

what

Allow IPv6 communication b/w VPCs over VPC peering

why

Application hosted in VPC-1 wants to access resources hosted in private subnet of VPC-2 over IPv6.

references

Nitin avatar

@Gabriela Campana (Cloud Posse) i checked. but this error not with the changes of my code.. can you help me with it.?

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

@Igor Rodionov is this a test failing due to opentofu / terraform concurrency?

1
Gabriela Campana (Cloud Posse) avatar
Gabriela Campana (Cloud Posse)

Nitin, we are chasing this internally and will get back to you asap

Gabriela Campana (Cloud Posse) avatar
Gabriela Campana (Cloud Posse)

@Igor Rodionov bumping this up

2024-09-16

2024-09-17

2024-09-18

Nitin avatar
1
Nitin avatar

@Erik Osterman (Cloud Posse) terratest is passed.

@Gabriela Campana (Cloud Posse) can you please assign someone for approval and merge

1
1
Gabriela Campana (Cloud Posse) avatar
Gabriela Campana (Cloud Posse)

@Andriy Knysh (Cloud Posse)

Gabriela Campana (Cloud Posse) avatar
Gabriela Campana (Cloud Posse)

@Igor Rodionov

Gabriela Campana (Cloud Posse) avatar
Gabriela Campana (Cloud Posse)

Merged

Gabriela Campana (Cloud Posse) avatar
Gabriela Campana (Cloud Posse)

These changes were released in v0.19.4.

Nitin avatar
#55 Allow setting `network_type` argument

Have a question? Please checkout our Slack Community or visit our Slack Archive.

Slack Community

Describe the Feature

Allow setting network_type argument in aws_elasticache_cluster managed by module.

Expected Behavior

Add module variable to set https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/elasticache_cluster.html#network_type

Use Case

I need to create memcached cluster with network_type = "dual_stack" in dualstack subnet.

Describe Ideal Solution

See ‘Expected Behaviour’

Alternatives Considered

Drop this module, manage aws_elasticache_cluster on my own.

Additional Context

None.

Gabriela Campana (Cloud Posse) avatar
Gabriela Campana (Cloud Posse)

@Igor Rodionov

Nitin avatar
#247 Dualstack support

what

Redis cluster can be run in 3 network modes - ipv4, ipv6 or dual_stack.
Underlying module already supports this parameter

why

It can be mandatory to enable it to be able to connect from dual_stack or ipv6 only runtimes

references

1
Gabriela Campana (Cloud Posse) avatar
Gabriela Campana (Cloud Posse)

@Igor Rodionov @Ben Smith (Cloud Posse)

#247 Dualstack support

what

Redis cluster can be run in 3 network modes - ipv4, ipv6 or dual_stack.
Underlying module already supports this parameter

why

It can be mandatory to enable it to be able to connect from dual_stack or ipv6 only runtimes

references

2024-09-19

Lennart Goedhart avatar
Lennart Goedhart
#55 docs: fix `logging` description

what

Fix the description and README documentation for the logging variable. It looks like it was copypasta from the kms_key_id variable description.

why

Because the description does not match the functionality.

    keyboard_arrow_up