Closed gillg closed 1 year ago
Thank you for contribution!✨
The docsite for this PR is available for download as an artifact from this run: https://github.com/ansible-collections/community.windows/actions/runs/3367498206
You can compare to the docs for the main
branch here:
https://ansible-collections.github.io/community.windows/branch/main
File changes:
M
collections/community/windows/win_format_module.htmlM
collections/community/windows/win_partition_module.html
Partition unique ID to select it.
+Common return values are documented here, the following are the fields unique to this module:
+Key |
+Description |
+
---|---|
+ |
Returned: success +Sample: |
+
SUMMARY
This PR group several changes around disks management :
" "
😅 I use the correlation between disk "Index" and "DiskNumber" and it seems cover all the possible cases.win_format
unique_id
(what can be reused inwin_format
) at the end ofwin_partition
win_initialize_disk
doesn't returns it (and it not aware of it), and that could make the way you select your partition number a little bit tricky. So having a way to really cleanup the disk in an idempotent way seems good. This thing could be a little bit dangerous (but less than randomly delefe the partition "0" at each run), so we only allows it if the filter returns 1 partition.Other module proposition
I also created a module win_disk_mount, I could share it but I don't have time to write any tests, make a perfect doc, examples, etc, so if you are interested someone should contribute a little bit. This is the minimal doc to understand it :
Minimal examples :
Let me know !