terraform version 1.4.5, when I try to run terraform state rm , it bombs out if resource is not present in terraform state file.
with 1.4.5
INFO[2023-04-24T12:15:55Z] executing command 'terraform state rm aws_s3_bucket_object.captain_file'
Removed aws_s3_bucket_object.captain_file
Successfully removed 1 resource instance(s).
INFO[2023-04-24T12:16:02Z] executing command 'terraform state rm aws_s3_bucket_object.manifest'
Removed aws_s3_bucket_object.manifest
Successfully removed 1 resource instance(s).
INFO[2023-04-24T12:16:10Z] executing command 'terraform state rm aws_s3_bucket.bucket'
`Error: Invalid target address`
No matching objects found. To view the available instances, use "terraform
state list". Please modify the address to reference a specific instance.
``
but with terraform 0.12.31, when I try to run terraform state rm , it passes to another step , if resource is not present in terraform state file mentioning no resource found.
with 0.12.31
INFO[2023-04-24T13:16:04Z] executing command 'terraform state rm aws_s3_bucket_object.manifest'
Removed aws_s3_bucket_object.manifest
Successfully removed 1 resource instance(s).
INFO[2023-04-24T13:16:06Z] executing command 'terraform state rm aws_s3_bucket.bucket'
No matching resource instances found.
INFO[2023-04-24T13:16:08Z] executing command 'terraform state rm aws_iam_role.edge_cors_lambda_role'
Removed aws_iam_role.edge_cors_lambda_role
Successfully removed 1 resource instance(s).
INFO[2023-04-24T13:16:09Z] executing command 'terraform state rm aws_iam_role.dex_lambda_at_edge'
No matching resource instances found.
is this an intentional change or can we preserve that behaviour from 0.12.31 in 1.4.5? Would really appreciate some guidance