Cli-microsoft365: New command: List enabled features

[phawrylak]

List features enabled on site collection

command: spo site feature list -u|--url <url>

• url: The URL of the site collection from which to list enabled features

List features enabled on site

command: spo web feature list -u|--webUrl <webUrl>

• webUrl: The URL of the site from which to list enabled features

[phawrylak]

Consider single command with --scope option:
spo feature list -u|--webUrl <webUrl> -s|--scope <scope>

[waldekmastykarz]

Let's go with spo feature list -u|--webUrl <webUrl> -s|--scope <scope>

[phawrylak]

I'll leave this for others, so feel free to take it, guys. 😃

[simonagren]

I can look at this soon :)

[waldekmastykarz]

All yours @simonagren! Thank you! 👏

[simonagren]

No probs man, glad to contribute in the humble ways I can :)

[waldekmastykarz]

And it's very much appreciated! 👏

[waldekmastykarz]

@simonagren Are you still working on this?

[simonagren]

I will finish the other prs tonight. I took a decision to go with the url.resolve.

This one I started to look at yersterday, and I had a look at some of the other commands on how to solve it. I could get a pr done on tuesday for this one

[simonagren]

@waldekmastykarz @VelinGeorgiev
Do you think we should have the option of "All" in the scope aswell, as in spo customaction list?

The custom action Rest result has scope included that is being utilized in the combined return values of all.
While Features we don't have the scope if we don't add it "manually".

So IF we allow for all as a scope, do we care about the scope of it in the result?

[simonagren]

If we match the PnP PowerShell Command, we should not allow for "All"

[waldekmastykarz]

I don't think an all scope makes sense in this case. Features have particular scope per definition and mixing site- and web-scoped features seems confusing.