fix(lightsail): Handle wildcard DNS entries with escaped asterisks

[alvarolb]

Fixes #44587

Description

AWS Lightsail API returns wildcard domain entries with asterisks escaped as \052 (octal notation). This causes Terraform to fail reading wildcard DNS
entries after creation and to detect drift on subsequent applies.

This PR fixes the issue by normalizing wildcard characters in two places:

1. FindDomainEntryById: Compare both * and \052 formats when searching for domain entries
2. flattenDomainEntryName: Convert \052 back to * before saving to state

Changes

• Modified internal/service/lightsail/domain_entry.go:
  • Updated FindDomainEntryById() to match entries using both wildcard formats
  • Updated flattenDomainEntryName() to unescape \052 to * for state consistency

Testing

Tested with:

• Terraform 1.5.7, 1.6.6
• AWS Provider 4.67.0, 6.15.0

Test scenario:

1. Create Lightsail instance with wildcard DNS entry (*.subdomain.example.com)
2. Verify creation succeeds without "empty result" error
3. Run terraform apply again to verify no drift is detected
4. Verify state stores * instead of \052

Before this fix:
Error: reading AWS Lightsail DomainEntry (*.test,example.com,A,1.2.3.4): empty result

After this fix:
Apply complete! Resources: 4 added, 0 changed, 0 destroyed.

Related Issues

• Similar fix for underscores: bugfix: aws_lightsail_domain_entry id field update separator to , to support _ in txt records #27791

Checklist

• Code follows the project's style guidelines
• Changes have been tested locally
• Issue linked (aws_lightsail_domain_entry fails to read wildcard DNS entries #44587)
• Acceptance tests pass (requires AWS account with Lightsail access)

Notes

This fix maintains backward compatibility with existing non-wildcard DNS entries while properly handling the escaped wildcard format returned by the AWS
Lightsail API.

[github-actions]

✅ Thank you for correcting the previously detected issues! The maintainers appreciate your efforts to make the review process as smooth as possible.

[github-actions]

Community Guidelines

This comment is added to every new Pull Request to provide quick reference to how the Terraform AWS Provider is maintained. Please review the information below, and thank you for contributing to the community that keeps the provider thriving! 🚀

Voting for Prioritization

• Please vote on this Pull Request by adding a 👍 reaction to the original post to help the community and maintainers prioritize it.
• Please see our prioritization guide for additional information on how the maintainers handle prioritization.
• Please do not leave +1 or other comments that do not add relevant new information or questions; they generate extra noise for others following the Pull Request and do not help prioritize the request.

Pull Request Authors

• Review the contribution guide relating to the type of change you are making to ensure all of the necessary steps have been taken.
• Whether or not the branch has been rebased will not impact prioritization, but doing so is always a welcome surprise.