-
-
Notifications
You must be signed in to change notification settings - Fork 18
Description
Found a bug? Maybe our Slack Community can help.
Describe the Bug
When using the resource awsutils_default_vpc_deletion in a module to delete VPCs in all regions, on apply I have a configuration that calls the resource (at least for the initial apply) around 700 times for various regions in AWS accounts throughout my AWS organization. Initially, the resource works as intended and completes within 1-2 seconds. Around the 75th call, it increases to around 7 minutes. It may complete another 10 or so resource calls within 2 seconds - 2 minutes but eventually will not complete any at all going on for hours trying complete the same resource calls.
Expected Behavior
Have all resources complete in the usual 1-2 second timeframe regardless of how many calls are made in succession, an if there is an issue have a reasonable timeout to move on to the next resource
Steps to Reproduce
Steps to reproduce the behavior:
module main.tf:
## Delete default VPC resource "awsutils_default_vpc_deletion" "default" { }
Parent module call:
`# Delete default VPC in all regions
module "default_vpc_useast1" {
source = "./modules/default-vpc"
vault_aws_role = var.vault_aws_role
region = "us-east-1"
}
module "default_vpc_useast2" {
source = "./modules/default-vpc"
vault_aws_role = var.vault_aws_role
region = "us-east-2"
}
module "default_vpc_uswest1" {
source = "./modules/default-vpc"
vault_aws_role = var.vault_aws_role
region = "us-east-1"
}
module "default_vpc_uswest2" {
source = "./modules/default-vpc"
vault_aws_role = var.vault_aws_role
region = "us-east-2"
}
module "default_vpc_cacentral1" {
source = "./modules/default-vpc"
vault_aws_role = var.vault_aws_role
region = "ca-central-1"
}
module "default_vpc_apnortheast1" {
source = "./modules/default-vpc"
vault_aws_role = var.vault_aws_role
region = "ap-northeast-1"
}
module "default_vpc_apnortheast2" {
source = "./modules/default-vpc"
vault_aws_role = var.vault_aws_role
region = "ap-northeast-2"
}
module "default_vpc_apnortheast3" {
source = "./modules/default-vpc"
vault_aws_role = var.vault_aws_role
region = "ap-northeast-3"
}
module "default_vpc_apsouth1" {
source = "./modules/default-vpc"
vault_aws_role = var.vault_aws_role
region = "ap-south-1"
}
module "default_vpc_apsoutheast1" {
source = "./modules/default-vpc"
vault_aws_role = var.vault_aws_role
region = "ap-southeast-1"
}
module "default_vpc_apsoutheast2" {
source = "./modules/default-vpc"
vault_aws_role = var.vault_aws_role
region = "ap-southeast-2"
}
module "default_vpc_eucentral1" {
source = "./modules/default-vpc"
vault_aws_role = var.vault_aws_role
region = "eu-central-1"
}
module "default_vpc_euwest1" {
source = "./modules/default-vpc"
vault_aws_role = var.vault_aws_role
region = "eu-west-1"
}
module "default_vpc_euwest2" {
source = "./modules/default-vpc"
vault_aws_role = var.vault_aws_role
region = "eu-west-2"
}
module "default_vpc_euwest3" {
source = "./modules/default-vpc"
vault_aws_role = var.vault_aws_role
region = "eu-west-3"
}
module "default_vpc_eunorth1" {
source = "./modules/default-vpc"
vault_aws_role = var.vault_aws_role
region = "eu-north-1"
}
module "default_vpc_saeast1" {
source = "./modules/default-vpc"
vault_aws_role = var.vault_aws_role
region = "sa-east-1"
}`
Screenshots
If applicable, add screenshots or logs to help explain your problem.
Environment (please complete the following information):
Anything that will help us triage the bug will help. Here are some ideas:
- OS: MacOS
- Version 10.6.1
- Terraform
- Version 10.11.4 darwin_arm24
- Provider
- Version 0.20.1
Additional Context
Not knowing what the module is doing, is there an API rate limit somewhere that is causing the issue?