[New Data Source]: Data zone domain

[dabcoder]

Description

This provider implements a resource for data zone domains: https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/datazone_domain. However it does not yet implement a data source for the same component. It seems to me that it'd be useful to have this implemented, because the domain is required when creating other resources, such as an environment or a project, and such domain may already exist in a given AWS account.

Requested Resource(s) and/or Data Source(s)

aws_datazone_domain. Reference in the Go SDK v2 here or there.

Potential Terraform Configuration

data "aws_datazone_domain" "example" {
  name = "DefaultDomain"
}

Which could then export the identifier and the Arn.

References

https://docs.aws.amazon.com/datazone/latest/userguide/datazone-concepts.html#what-are-domains
https://docs.aws.amazon.com/datazone/latest/APIReference/API_GetDomain.html
https://docs.aws.amazon.com/datazone/latest/APIReference/API_ListDomains.html

Would you like to implement it?

Yes

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

[github-actions]

Warning

This Issue has been closed, meaning that any additional comments are much easier for the maintainers to miss. Please assume that the maintainers will not see them.

Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed.