Future of the provisioning engine

[johnnycardy]

My understanding is that there is no immediate plan to port the PnP Framework provisioning engine over to PnP Core. Is that correct? But, this would be expected at some point in the future?

Could someone clarify the reasons for this - is it simply a question of pure workload, or is it also the case that PnP Powershell provisioning is the expected future route forward (it does seem to be massively popular).

Finally, if one were to begin work on a new provisioning engine implementation within PnP Core, would the expectation be that it follows a similar pattern to the current PnP Framework implementation, or would it be expected to be implemented in a significantly different way? For example, I guess there would be a focus on DI and unit test coverage, but other than that - it would use the pre-existing template format, for example?

Thanks.

[johnnycardy]

@jansenbe can you give any insight? I intend to build a. Net provisioning solution to plug a number of gaps I see with PnPFramework and I'm curious about whether an open source contribution would be welcome.

[johnnycardy]

I think I have now answered this question myself. This is my current opinion:

PnP Framework is in need of updates, but it makes more sense to work on that via either a fork, or ideally, PRs would be accepted. I don't see the value in writing a new provisioning engine in the PnPCore project. Especially since PnPFramework references and can use PnPCore.

[Magnus-K-work]

As a user of this and a few other SharePoint frameworks, I think that Microsoft makes it clear that this (as well as PnP Powershell) is a "community contribution driven" framework. So, if I need a fix or an addition then Microsoft expects me to write it and submit as a PR to that framework.

I have an opinion about that, but this is Microsoft's decision so I will not judge that. All I know is that I feel that the community does not seem to want to put work into PnP Core.

I was trying to use PnP Core, but found a number of showstoppers for my use and had to decide to use another framework (MS Graph REST API) to make my deadline.

[johnnycardy]

The issue for me is that unfortunately there is very little community engagement.

I have submitted several simple PRs to check how quickly they can be merged and they haven't been reviewed after weeks.

This leaves me also in the position of needing to come up with a new solution.

In my case, that's my own fork will that I can actually make improvements.