Loading...
Loading...
### Terraform Version ```shell Above all the 5.1.0 provider versions ``` ### Terraform Configuration Files ``` resource "aws_ssm_document" "foo" { name = "test_document" document_type = "Command" content = <<DOC { "schemaVersion": "1.2", "description": "Check ip configuration of a Linux instance.", "parameters": { }, "runtimeConfig": { "aws:runShellScript": { "properties": [ { "id": "0.aws:runShellScript", "runCommand": ["ifconfig"] } ] } } } DOC } terraform { required_providers { aws = { source = "hashicorp/aws" version = "5.2.0" } } } provider "aws" { region = "us-east-1" assume_role { role_arn = "arn:aws:iam::0000000000:role/XYZ" session_name = "Test_Provisioner" external_id = "Test" } ``` ### Debug Output ``` Plan: 0 to add, 0 to change, 1 to destroy. aws_ssm_document.foo: Destroying... [id=test_document] ╷ │ Error: waiting for SSM Document (test_document) delete: InvalidDocument: No matching value was found for Name. ``` ### Expected Behavior document destroyed successfully ### Actual Behavior Plan: 0 to add, 0 to change, 1 to destroy. aws_ssm_document.foo: Destroying... [id=test_document] ╷ │ Error: waiting for SSM Document (test_document) delete: InvalidDocument: No matching value was found for Name. ### Steps to Reproduce 1. terraform init 2. terraform plan 3. terraform apply 4. terraform destroy ### Additional Context When trying to destroy SSM document created by any provide version above 5.1.0 is failing stating Error: waiting for SSM Document (test_document) delete: InvalidDocument: No matching value was found for Name. Meanwhile if we use any version below 5.0.0 it is being able to destroy the document succesfully ### 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.