Cli-microsoft365: New command: spo report OneDriveUsageAccountDetail

[plamber]

Usage

spo report OneDriveUsageAccountDetail [options]

Description

Gets details about OneDrive usage by account.

Options

| Option | Description |
| ----------------------- | ----------------------------------------- |
| -o, --option <option> | option |
| -o, --output [output] | Output type. json\|text. Default text |
| -p, --period [period] | The length of time over which the report is aggregated. Supported values D7,D30,D90,D180
| -d, --date [date] | The date for which you would like to view the users who performed any activity. Supported date format is YYYY-MM-DD. Specify the date or period, but not both.
| -f, --outputFile [outputFile] | Path to the file where the Office 365 Groups activity by group report should be stored in.| --verbose | Runs command with verbose logging |
| --debug | Runs command with debug logging |

Additional Information

Implements

Will be placed under "SPO" -> "report"

You can assign it to me.

[VelinGeorgiev]

I left the same comment in the PR, but here is again:

@waldek, @garrytrinder should we move this to its own separate section specific to onedrive?
I see this command more like onedrive report activityfilecounts. We did not have any onedrive commands till this point, maybe this is from where the confusion comes.

@plamber , I am sorry for the delay that question might cause, but we have to sort where logically the onedrive commands should be added.

[plamber]

@VelinGeorgiev, @waldekmastykarz: indeed, I had the same thought initially. I was about to ask you the same. But once I saw that everything else is residing in SPO, I moved it there.

My worry was that the reports will be the only commands lying under OneDrive

[VelinGeorgiev]

No worries, that is perfectly fine with me. The OneDrive APIs will be something we can explore in the future, and they definitely deserve its own namespace in the CLI. They are in my todo list as well, my problem is that I have pretty long todo list.

Let's wait and see what is @garrytrinder and @waldekmastykarz opinion.

[plamber]

@VelinGeorgiev: you can rely also on me if you want to tackle your long todo list :)

[garrytrinder]

Good catch @plamber & @VelinGeorgiev

I agree with @VelinGeorgiev that these reports are put under onedrive namespace, gives us a place to add more OneDrive specific commands in the future.

[plamber]

@VelinGeorgiev: I am fine with this. Do you want me to do all changes? Or are you going to make these while you are checking the code?

[waldekmastykarz]

+1 for onedrive. Good catch @VelinGeorgiev

[VelinGeorgiev]

@plamber, would you be able to change the onedrive commands? Lets rename and move the report commands under folder:

-- onedrive
    -- reports  

I can make changes while checking the commands as well if I get to do reviews before you.
Thanks!

[plamber]

Will do it by next week