Get-VmsStorageInfo / Get-VmsCameraStorageInfo / Send-VmsDriverCommand

[Silex]

Should we add these to the repo? As main commands or as 3rd party "best effort" ?

[Silex]

Also just mentionning Send-VmsDriverCommand bugs with binary data (e.g hitting /axis-cgi/jpg/image.cgi), not sure this needs fixing tho.

[Silex]

After some thoughts I think we should at least include Send-VmsDriverCommand to this project as a supported command, it makes sense for automation.

But I'd also understand that you might want to minimize the amount of supported "tricky" commands...

[joshooaj]

I'm okay with adding Send-VmsDriverCommand as we're still just exposing an existing MIP SDK feature in a powershell-friendly way. For "tricky" commands like these we should make it clear in the docs that they're a bit advanced, provide a couple of examples, and do the best we can at explaining the parameters.

I'm hesitant about adding commands like Get-VmsStorageInfo to the module. The example functions were provided as examples of how you can build your own reports with the module. But inevitably it encourages folks to ask for the command to be extended in various ways. I had never intended Get-VmsCameraReport to be such an enormous report for example.

Is there a middle ground where we make the examples more easily accessible / usable without adding them directly to the module?

[Silex]

Sounds good to me. Add Send-VmsDriverCommand to the module and put the Get-Vms*Info as examples somewhere in the repo, maybe https://github.com/milestonesys/MilestonePSTools/tree/main/docs/examples

That way people can still do PR for both but it's clear which one is "supported" and which ones aren't.