Cli-microsoft365: New command: tenant service message list

Created on 26 Jul 2020  路  13Comments  路  Source: pnp/cli-microsoft365

Usage

tenant service message list [options]

Description

Gets the service messages regarding services in Office 365 from the Office 365 Management API

Options

| Option | Description |
| ----------------------- | ----------------------------------------- |
| -w, --workload [workload] | Allows retrieval of the service messages for only one particular service. If not provided, the service messages of all services will be returned. |
| -o, --output [output] | Output type. json,text. Default text |
| --verbose | Runs command with verbose logging |
| --debug | Runs command with debug logging |

Additional Information

For more information and implementation details see Get-PnPOffice365ServiceMessage

feature request new feature work in progress

Most helpful comment

Hi @waldekmastykarz @garrytrinder @rabwill
Submitted PR. Please review.

All 13 comments

Hi @rabwill
Can I take this up?

All yours @nanddeepn 馃槉

Since the API in its schema refers to services rather than workloads, shall we use -s --service rather than workLoad? Also, it would be good to clarify what's the expected value: service ID or its display name, but perhaps that will be clarified in examples.

@waldekmastykarz I like that idea because of its intuitive nature although this spec was written like for like with the PnP PowerShell commands and Office 365 services are always also documented in MSFT documents as workloads.

Ah sorry. I must have been looking at a different API. Since the API returns workload in its response, won't it be confusing if we let users filter by service?

So let's keep it as is then. At least we are consistent with the terms used in MSFT docs.

If we stick with workload and is the term that MS are using then maybe we should be referring to these commands as tenant workload and use workload throughout instead of service to be consistent.

The trouble is that the API is named Service Communications API so if we use workload in the command namespace, we could risk discoverability as people coming from the docs would be looking for service rather than workload 馃檨

I see, so inconsistency is consistency, in this case. Classic MS 馃槀

So folks, just to double check @waldekmastykarz and @garrytrinder no change in spec right? 馃槉

The only thing I'd change is to spell workload all lowercase as it's one word 馃槉

Done 馃槂

Hi @waldekmastykarz @garrytrinder @rabwill
Submitted PR. Please review.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

aakashbhardwaj619 picture aakashbhardwaj619  路  3Comments

arjunumenon picture arjunumenon  路  3Comments

vineet2907 picture vineet2907  路  3Comments

garrytrinder picture garrytrinder  路  3Comments

joshua-probst picture joshua-probst  路  3Comments