-
Notifications
You must be signed in to change notification settings - Fork 455
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add disk stats for datastore #1896
Conversation
1c5aa7c
to
82c6d6e
Compare
Marked pull request as a draft until Ready for Review. |
82c6d6e
to
97e4bfc
Compare
@tenthirtyam I completed the feature, however I had trouble running the acceptance tests with the following error:
Although I set the relevant env vars. I don't know if there is something I am missing about the unit tests setup. |
97e4bfc
to
0d979ae
Compare
@nikfot Via environment variables you need to configure the username/password and Address of the vsphere server:
Please keep in mind this will create and destroy resources against the vCenter instance, so make sure its done against a non-production environment |
0d979ae
to
f1f6787
Compare
@appilon thanks! i had the TF_VAR_ set to user etc and I thought it would be enough. Anyway, I ran the acceptance tests successfully. Please proceed with the review. |
f1f6787
to
6b7653a
Compare
@tenthirtyam any update on this one? |
Hello, |
Unfortunately, not at this time due to other priorities. |
@tenthirtyam that's totally understandable, but is there a standard process about it? How and when will it be discussed etc. This addition would be really helpfull since me and a bunch of other people will use it in vmware production environments. I also have more things that I would like to contribute, but if they are not going to be concidered it would be in vain. I would also like to contribute more to the community as far as issues and more are concidered and the current PR is on a "to know us better basis", that is why I am asking. |
6b7653a
to
969db34
Compare
Hello, Since I have no remaining task on my side, please give me some feedback on this pull request. Thanks, |
Hi @nikfot IMHO it is good to go into the next release. We won't have any more releases this year due to stability reasons. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, just a quick look and I notice that the data source documentation needs to be updates along with this change.
Add total capacity and free space for datastore. This way more criteria can be added to datastore selection Add list of datastores with free space and total capacity. Enhance documentation for datastore data source. Add documentation for datastore stats data source. Signed-off-by: nikfot <nik_fot@hotmail.gr>
969db34
to
61276fc
Compare
Hello @tenthirtyam && @vasilsatanasov and belated wishes for a happy 2024! @tenthirtyam I added the necessary documentation. Please check it out and let me know if it is good to go for the next release. Thanks, |
Hello @tenthirtyam! Did you find time to review tge additions? |
@tenthirtyam @vasilsatanasov could someone provide a feedback on this one please? |
any news on this one? will it be on the next release? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
thanks @tenthirtyam . will these changes be on the 2.7.0 release? |
Yes. |
This functionality has been released in v2.7.0 of the Terraform Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
I'm going to lock this pull request 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 related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Description
There is currently no straightforward way to choose a datastore based on usage when creating a VM. This way more criteria can be added to choosing a datastore for a VM. For example, select a datastore if the total capacity is greater than a value or free space is greater than a value. I intend to also add a sorting of all datastores as part of this PR.
Add total capacity and free space for datastore. This way more criteria can be added to datastore selection
Acceptance tests
Have you added an acceptance test for the functionality being added?
No, will be added after first feedback.
Have you run the acceptance tests on this branch?
Yes
Output from acceptance testing:
Release Note
Release note for CHANGELOG:
References
Close #1893