d/domain: add support to use name

[insidepacket]

Code of Conduct

• I have read and agree to the project's Code of Conduct.
• Vote on this issue by adding a 👍 reaction to the original issue initial description to help the maintainers prioritize.
• Do not leave "+1" or other comments that do not add relevant information or questions.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Description

When using domain data resources, support for using the name of the workload domain instead of the domain ID is preferred when retrieving a domain data resource.

Use Case(s)

Using the domain ID is time-consuming and not aligned with common practice. We should support using the name of the workload domain to retrieve a domain data resource.

Potential Configuration

data "vcf_domain" "example" {
  name = var.vcf_domain_name
}

References

No response

[burnsjared0415]

i can pick up if ok

[tenthirtyam]

Assigned to Jared Burns, VMware by Broadcom.

[github-actions]

I'm going to lock this issue because it has been closed for 30 days. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.