Skip to content
docsv0.13.1

PluginManagementPlugin

The plugin that makes plugin management reachable. It is the one plugin a host adds by hand; from there every other one can be installed and toggled from whatever surface the host runs — terminal, admin panel, or an MCP client — because the kernel discovers {@see operations()} on any booted plugin and each projector materialises them into its own shape. Both collaborators come from the container. The registry is required — with no store there is nothing to manage. The installer is optional: a host that never wired one still lists and toggles what it has, and simply does not offer the operations that would reach the network.

PluginManagementPlugin::__construct()

public function __construct(Milpa\Interfaces\Di\DIContainerInterface $container):

Parameters

Parameters of __construct()
NameTypeDescription
$containerMilpa\Interfaces\Di\DIContainerInterface

PluginManagementPlugin::boot()

public function boot(): void

Nothing to boot: this plugin contributes operations, it does not run.

PluginManagementPlugin::install()

public function install(): void

Nothing to set up: this plugin owns no data of its own.

PluginManagementPlugin::uninstall()

public function uninstall(): void

Nothing to tear down — removing this plugin removes only the ability to manage the others, never the others themselves.

PluginManagementPlugin::enable()

public function enable(): void

Nothing to switch on: the operations appear because the kernel found them, not because anything was started here.

PluginManagementPlugin::disable()

public function disable(): void

Nothing to switch off.

PluginManagementPlugin::operations()

public function operations(): array

The plugin-management operations, built against whatever this host wired: the registry is required, the installer is not.

Throws

\RuntimeException when no registry is in the container