Allow Windows MDM commands GET verb

[georgekarrv]

Goal

User story
As a user,
I want to run Windows mdm commands with the Get Access Type (verb),
so that I can retrieve useful data supported by Windows CSPs.

Context

• Requestor(s): _____
• Product designer: _____

Changes

Allow mdm commands to support in addition to the we currently allow.

Product

• [ ] UI changes: TODO
• [ ] CLI usage changes: TODO
• [ ] REST API changes: TODO
• [ ] Fleet's agent (fleetd) changes: TODO
• [ ] Permissions changes: TODO
• [ ] Outdated documentation changes: TODO
• [ ] Changes to paid features or tiers: TODO

Engineering

• [ ] Database schema migrations: TODO
• [ ] Load testing: TODO

ℹ️  Please read this issue carefully and understand it. Pay special attention to UI wireframes, especially "dev notes".

QA

Risk assessment

• Requires load testing: TODO
• Risk level: Low / High TODO
• Risk description: TODO

Manual testing steps

1. Step 1
2. Step 2
3. Step 3

Testing notes

Confirmation

1. [ ] Engineer (@____): Added comment to user story confirming successful completion of QA.
2. [ ] QA (@____): Added comment to user story confirming successful completion of QA.

[noahtalerman]

Thanks for tracking this one @georgekarrv.

so that I can retrieve useful data supported by Windows CSPs

What data exactly is useful? Did this come up in a testing/QA workflow? If so, what was the workflow?

I think we want to dig into the specific problem/pain so we can flesh out the user story.

[georgekarrv]

With QA wolf I wanted to have them test windows mdm commands without affecting the VM's.

Most of the exec commands include things like Reboot RemoteWipe InstallMicrosoftOffice which aren't simple things for QA wolf to test and not break the VM.

There are plenty of Get's that also seem useful to IT in general

• Accounts
• Bitlocker
• DevDetail
• DeviceStatus
• DevInfo
• DiagnosticLog
• Reporting