[Bug]: Deleted AWS Backup Vault Lock configurations aren't recreated

[andy-careplanner]

Terraform Core Version

1.3.6

AWS Provider Version

4.40.0, 4.46.0

Affected Resource(s)

aws_backup_vault_lock_configuration

Expected Behavior

Terraform should recreate an AWS Vault Lock if it has been deleted but still exists in the configuration.

Actual Behavior

Terraform does not detect that the Vault Lock has been deleted.

Relevant Error/Panic Output Snippet

No response

Terraform Configuration Files

resource "aws_backup_vault" "foo" {
  name        = "foo"
}

resource "aws_backup_vault_lock_configuration" "foo" {
  backup_vault_name   = aws_backup_vault.foo.id
}

Steps to Reproduce

1. Apply the example configuration so that the 'foo' AWS Backup Vault and Vault Lock are created
2. In the AWS console delete the Vault Lock
3. Run a plan/apply of the example configuration, no changes are detected

Note that deleting the Vault Lock AND the Vault then running a plan causes Terraform to propose recreating both of them. But if you just delete the Vault Lock, Terraform doesn't notice.

Debug Output

No response

Panic Output

No response

Important Factoids

No response

References

No response

Would you like to implement a fix?

None

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please see our prioritization guide for information on how we prioritize.
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.

[smittnacht]

Able to reproduce this with v5.37.0 of terraform-provider-aws