#terraform-aws-modules (2023-10)
Terraform Modules
Discussions related to https://github.com/terraform-aws-modules
Archive: https://archive.sweetops.com/terraform-aws-modules/
2023-10-03
![getSurreal avatar](https://avatars.slack-edge.com/2019-12-03/846988219299_7894b3fb8c1157b2f48f_72.jpg)
Are the terratest runs for all the modules published publicly anywhere?
![jose.amengual avatar](https://secure.gravatar.com/avatar/32f267b819eac9e0ea6a8324b53064a0.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0024-72.png)
they are on the PRs status
![jose.amengual avatar](https://secure.gravatar.com/avatar/32f267b819eac9e0ea6a8324b53064a0.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0024-72.png)
you can check the latest PR
![getSurreal avatar](https://avatars.slack-edge.com/2019-12-03/846988219299_7894b3fb8c1157b2f48f_72.jpg)
Ok, I see. Thanks. So they are not run on a schedule? Our S3 module is modeled after yours and our tests have been failing on deletion since the release of AWS provider 5.17.0. Forcing it to <5.17 works. With that in mind I wanted to see if your s3-module is showing the same behaviour. The last PR merge on your s3 module was 8/25 but AWS 5.17 was 9/14.
![jose.amengual avatar](https://secure.gravatar.com/avatar/32f267b819eac9e0ea6a8324b53064a0.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0024-72.png)
is not mine, it’s CloudPosse
![jose.amengual avatar](https://secure.gravatar.com/avatar/32f267b819eac9e0ea6a8324b53064a0.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0024-72.png)
![jose.amengual avatar](https://secure.gravatar.com/avatar/32f267b819eac9e0ea6a8324b53064a0.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0024-72.png)
but no, they do not run on schedule
![jose.amengual avatar](https://secure.gravatar.com/avatar/32f267b819eac9e0ea6a8324b53064a0.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0024-72.png)
and they do not updater the providers all the time so if you create a PR to change something then you could force the provider change and see
![Erik Osterman (Cloud Posse) avatar](https://secure.gravatar.com/avatar/88c480d4f73b813904e00a5695a454cb.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0023-72.png)
We run tests on PRs and merge to main
2023-10-11
2023-10-14
![johan l avatar](https://secure.gravatar.com/avatar/df6fc1011c34ac6a69a263345523aa96.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0005-72.png)
Hello, I have made a PR on one of the AWS modules a few weeks ago. I have not yet had a reply is there a specific way to get the review process started ? https://github.com/cloudposse/terraform-aws-vpc/pull/124
what
This PR adds support for Network Address Usage Metrics on the VPC.
AWS documentation : https://docs.aws.amazon.com/vpc/latest/userguide/network-address-usage.html
Terraform documentation : https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/vpc#enable_network_address_usage_metrics
why
Network Address Usage metrics can help monitor the growth of a VPC and would be useful for any user.
Enable this after creating a VPC does not trigger recreation of the VPC.
references
closes #115
2023-10-16
![Josh B. avatar](https://avatars.slack-edge.com/2022-05-23/3590168213712_fc95e4468b027cdca900_72.png)
Old pr here but is it possible for someone to take a look? https://github.com/cloudposse/terraform-aws-ecr/pull/103
• Allow to use ECR replication • https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/ecr_replication_configuration
Closes #99
![Gabriela Campana (Cloud Posse) avatar](https://avatars.slack-edge.com/2023-05-17/5281506983315_fbbf3b358313efef4647_72.jpg)
please see comments
• Allow to use ECR replication • https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/ecr_replication_configuration
Closes #99
2023-10-17
2023-10-21
![Hans D avatar](https://secure.gravatar.com/avatar/4f534e0b78001931f441c8011a95edeb.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0000-72.png)
anyone experience with github-runners that scale (also) based on the size of the queue size for outstanding actions ?
![Max Lobur (Cloud Posse) avatar](https://avatars.slack-edge.com/2021-07-20/2316891735296_3098d8d2760936592f52_72.jpg)
Scale GitHub Runners based on the number of queued jobs in GitHub Actions
![Jeremy G (Cloud Posse) avatar](https://avatars.slack-edge.com/2020-07-04/1229022582372_22757dbc9ef96d371614_72.jpg)
We are adding support (in terraform-aws-components) for the new GitHub-supported Runner Scale Sets which launch an ephemeral runner for each job queued. Actions should never need to wait for longer than it takes to launch a runner. Our support should be published in a week or two.