The new ProvisionerStrategy doesn't call this extension point unlike the default one (here and there)
This can lead to invalid/inconsistent behaviour with implementations of this extension point.