On the surface, this looks like a cool idea and is similar to how MODX (www.modx.com
) handles add-ons. However, things can get messy really quick if the rollback isn't handled properly. For instance, the most recent Blog update makes significant changes to the database and can easily break a blog implementation. Imagine an end-user upgrading the Blog module and then upgrading a few others then discovering that their blog is totally hosed. Would the rollback work? Not too keen on giving end-users the ability to mess with adding modules that, in my opinion, should be versioned as part of a Git repository with Composer. SilverStripe has always kept the CMS focused on managing content, not code...and with good reason. Security updates and modules should really be handled by a development team to insure that nothing breaks and that rollouts of new versions are done cleanly with backups. Not only that but what good is installing a module via the CMS if you can't manage the code from within the CMS. Seems moot.