dns_suffix_list prepends to searchable domains instead of appending

Community Guidelines

[X] I have read and agree to the HashiCorp Community Guidelines .
[ ] 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.

Terraform

1.3.6

Terraform Provider

3.0

VMware vSphere

7.0.3

Description

Leveraging the VSphere terraform provider, and when creating a vm with the use of the "dns_suffix_list", we've noticed that this field prepends the specified domains to the search field within the resolv.conf file. We would expect the "dns_suffix_list" to append, so that the primary domain (upon vm creation) remains the main domain searched against first, before checking against the other dns suffixes.

Affected Resources or Data Sources

resource/vsphere_virtual_machine

Terraform Configuration

clone { timeout = 120 template_uuid = data.vsphere_content_library_item.item.id dns_suffix_list = ["test2.com", "test3.com"] }

Debug Output

search test2.com test3.com.com test1.com

Panic Output

No response

Expected Behavior

Expected behavior is for the searchable domains to be in appended order:

search test1.com test2.com test3.com

Actual Behavior

The actual behavior is that the searchable domains are in prepended order:

search test2.com test3.com test1.com

Steps to Reproduce

define searchable domains as a tf list variable
configure vm with searchable domains variable as value for dens_suffix_list
create vm
log into vm and cat resolv.conf (primary domain will be last entry for "search")

Environment Details

No response

Screenshots

No response

References

No response

hashicorp / terraform-provider-vsphere