Repository navigation
v0.0.5
Pre-releaseThe change in this release is the whipped by wiskess command no longer needs a list of files that you would like to process. Now you have the option of specifying which file(s) you want to process or just providing the link to the files, i.e. Azure storage or AWS S3 link. I had to convert the original whipped.ps1 script to rust to make it operable in Linux and more reliable.
An example command is:
.\wiskess_rust.exe whipped -l "X:\" --start-date 2025-01-01 --end-date 2025-03-27 --in-link "https://myaccount.blob.core.windows.net/my-blob?sv=...%3D" --out-link "https://myaccount.file.core.windows.net/my-processed-files?sv=...%3D"Note that this doesn't currently support disk images. Hence I have kept the original whipped.ps1 functionality, which you can access using the old-whipped command and providing the data list.
This merges the branch where the whipped.ps1 script has been ported into rust. This has the same functionality as the original whipped.ps1 script, where collections are downloaded from azure storage or aws s3, pre-processed, passed to wiskess and the results uploads to either azure or aws.
The whipping of collections is now possible with only providing the --in-link, which is used to list the available collections or disk images. That list is then used to iteratively process all the collections in the cloud storage. You can optionally provide a list of data to process, which is the same as the prior whipped version.
Note: processing of disk images is still in development with this new version of whipped. Hence I have kept the old version, which you can access using the command old-whipped
Other features include making sure it is being run from an elevated terminal, added the template for srum-dump that was missing before, and updated the EZtools suite to use dotnet9.
What's Changed
- Test whip by @vividDuck in #8
- add dotnet9 setup for windows and linux by @vividDuck in #9
Full Changelog: v0.0.4...v0.0.5