federation

Multi-source plugin resolution integrates local, team, and public registries to manage dependencies. You configure registry sources with defined priorities so the system can pull plugins securely and consistently from multiple locations.

A lockfile ensures reproducible environments through deterministic version pinning. It synchronizes plugin dependencies across distributed systems, guaranteeing that deployments remain consistent and secure regardless of where they are executed.

Security policy enforcement applies defined rules to control which plugins can be used from any connected source. By configuring these policies, you restrict untrusted public registry plugins and ensure only approved dependencies are resolved.

Yes, you can configure local and team-specific registries alongside public ones by assigning priority levels. This multi-registry support allows you to define trusted internal sources first, ensuring secure and organized dependency resolution.

To set up a local plugin registry, use the command interface to add your directory and assign it a priority. This configuration, combined with lockfile synchronization, establishes the trusted source needed for deterministic deployments.

Without a lockfile, dependency resolution lacks deterministic version pinning, causing inconsistent plugin versions across environments. Generating a lockfile enforces synchronization and ensures reproducible deployments in distributed systems.