Loading...
Loading...
### Terraform Version ```shell Terraform v1.7.2 on linux_amd64 + provider registry.terraform.io/hashicorp/aws v4.67.0 ``` ### Terraform Configuration Files ```hcl resource "aws_glue_dev_endpoint" "test" { name = "test-dev-endpoint" role_arn = aws_iam_role.test.arn security_configuration = aws_glue_security_configuration.test.id } ``` ### Debug Output terraform deleted other aws glue resources on the script except for aws glue dev endpoints ### Expected Behavior Terraform destroy command should have deleted the glue dev-endpoint ### Actual Behavior Created a simple terraform script which created few other resources like aws-glue-connection, aws-glue-trigger, aws-glue-job etc Terraform destroy deleted the remaining resources from the .tf file and didn't delete the devendpoint. Due to this the dev-endpoint kept running in AWS and incurred costs. ### Steps to Reproduce ```console $ terraform init $ terraform apply $ terraform destroy ``` ### Additional Context Also, in AWS Glue portal, their is no direct option on the UI to check the glue development endpoints. Since Terraform destroy didn't work hence the resource was deleted manually using AWS CLI delete-glue-endpoint command. ### References _No response_ ### Generative AI / LLM assisted development? _No response_
Click on a version to see all relevant bugs
Terraform Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.