feat(directory): add argument enable_directory_data_access to aws_directory_service_directory

[ramonvermeulen]

Rollback Plan

N/A

Changes to Security Controls

N/A

Description

Adds the ability to enable directory data access via the provider.

Relations

Closes #44636

References

https://docs.aws.amazon.com/cli/latest/reference/ds/enable-directory-data-access.html
https://pkg.go.dev/github.com/aws/aws-sdk-go-v2/service/directoryservice#Client.DescribeDirectoryDataAccess
https://pkg.go.dev/github.com/aws/aws-sdk-go-v2/service/directoryservice#Client.EnableDirectoryDataAccess
https://pkg.go.dev/github.com/aws/aws-sdk-go-v2/service/directoryservice#Client.DescribeDirectoryDataAccess

Output from Acceptance Testing

Test execution:

❯ make testacc TESTS=TestAccDSDirectory_enableDirectoryDataAccess PKG=ds

make: Verifying source code with gofmt...
==> Checking that code complies with gofmt requirements...
make: Running acceptance tests on branch: 🌿 f/44636-enable-directory-data-access 🌿...
TF_ACC=1 go1.24.8 test ./internal/service/ds/... -v -count 1 -parallel 20 -run='TestAccDSDirectory_enableDirectoryDataAccess'  -timeout 360m -vet=off
2025/10/22 10:01:46 Creating Terraform AWS Provider (SDKv2-style)...
2025/10/22 10:01:46 Initializing Terraform AWS Provider (SDKv2-style)...
=== RUN   TestAccDSDirectory_enableDirectoryDataAccess
=== PAUSE TestAccDSDirectory_enableDirectoryDataAccess                                                                                                                                        --- PASS: TestAccDSDirectory_enableDirectoryDataAccess (1825.97s)
PASS
ok      github.com/hashicorp/terraform-provider-aws/internal/service/ds 1830.293s

[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.

[github-actions]

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