Service Extensions¶
The marketplace also hosts service extensions (xservices) — a
separate catalog from plugins, for reusable service-shaped dependencies a
plugin might need (databases, caches, message queues...). The service
command group mirrors plugin one-for-one, just pointed at that other
catalog.
Not xcli services
xcli service (singular, this page) is the marketplace catalog.
xcli services and xcli manager services (plural) show your
local xcore runtime's own service status — an unrelated command
that happens to share a similar name. If a command errors with
something about your local ServiceContainer, you probably typed the
plural by mistake.
Discovery¶
Read-only, public, no credentials required — same shape as Plugin Marketplace:
--sort accepts newest (default), installs, or rating — note
installs, not downloads; the service catalog counts installs, not
downloads.
Installing¶
Same two credentials as plugins — see Authentication
(xcli login covers both catalogs at once; a project-scoped key is
per-catalog, so make sure the project you created it for has
kind=service).
Installed extensions land in the directory configured under
marketplace_services.directory in integration.yaml (defaults to
./services) — deliberately a separate key from plugins.directory and
from services.databases.* (xcore's own internal service container
config), which already both use services/plugins for something else.
Management Commands¶
Identical shape to plugin:
Smaller surface than plugin
There's no service local/service runtime/service security/
service update today — service extensions don't have the same
local-dev-scaffolding or hot-reload workflow plugins do. Everything
that exists lives directly under xcli service.