Beta endpoints for MSgraph

[appieschot]

We have had the stance that we should do what we do with v1 whenever we can, and I totally agree with that. However some functionality is only available in the beta. A great sample is the way we retrieve planner tasks; it works fine with the v1 endpoint. Yet we are lacking the priority field.

Could we consider having either a beta property to retrieve that information as having an additional command just for the priority feels off as well.

[waldekmastykarz]

It's perfectly fine for us to use the beta endpoint if there's a need for it, as long as in the command docs we clearly state that the command is using preview functionality that might change without upfront notice to make our users' expectations.

[appieschot]

Happy to implement that if we feel that is the way forward, not really having strong feelings about it. If would implement it that way would it then make sense to always get those additional properties or add a --retrieveBetaInfo or --extended flag to retrieve the properties only when explicitly requested?

[waldekmastykarz]

If we introduced an extra option, what would it mean when the extra property gets out of beta and we can merge it on v1.0? Would that mean that we need to deprecate the option and introduce a breaking change at some point because we no longer need it?

[appieschot]

We could keep the option and retrieve new extended info whenever the beta endpoint provides it. We would only need to deprecate that option if the beta endpoint no longer provides additional info and we will no longer use it. However it could also be that whenever the property is moved out of beta new other properties are added to beta. I do not have insights how that process works; but my experience so far is that there are almost always some properties / settings you can only retrieve with beta.

[waldekmastykarz]

What if we keep whatever we have on v1.0, add an extra call for the things that we need from beta, get the extra stuff from beta response and merge it with the response from v1.0 and send to output, in our docs call out which properties we're retrieving from beta and what could change? In this case we'd be clearly managing expectations, we'd minimize the risk, solve our needs all at the cost of an extra call that we hopefully will be able to merge onto v1.0 when the API gets updated.

[appieschot]

I'll update specs and PR accordingly