Add support for datastore selection

[nikfot]

Community Guidelines

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

Description

There is no support for selecting datatore for a VM based on the datastore statistics. Even SDRS is not an absolute way on defining the specific datastore to use for a vm.

Moreover there is no access to datastore elements besides name and ID. You cannot get the numbers concerning a datastore using terraform data.

Use Case(s)

If a VM cluster has access to more than one datastores it would be very usefull if you did not have to hardcode the datastore, but instead instruct terraform to use the datastore with the less used space.

SDRS is using its own criteria to manage vms which - as long as our experiments go - it does not seem to conform fully with our own criteria ( please let me know If I am missing something ).

Potential Terraform Provider Configuration

We could add an capacity object on the vsphere_datastore and use it in a vsphere_datastore_policy attribute.

References

No response

[github-actions]

Hello, nikfot! 🖐

Thank you for submitting an issue for this provider. The issue will now enter into the issue lifecycle.

If you want to contribute to this project, please review the contributing guidelines and information on submitting pull requests.

[nikfot]

Hello,

Any updates on this issue & its merge request?

[github-actions]

Marking this issue as stale due to inactivity in the past 180 days. This helps us focus on the active issues. If this issue is reproducible with the latest version of the provider, please comment. If this issue receives no comments in the next 30 days it will automatically be closed.
If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

[nikfot]

This issue is not stale, there is an open PR waiting for review.

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