Plugins: An internals deep dive
summary
Explains that Spinnaker adds a JVM plugin system built on pf4j with per-plugin classloaders for dependency isolation and Spring child application contexts so plugins can auto-wire and promote extensions into core services. Describes two extension models: stable, typed extension points and unsafe, full-internal APIs, and the artifact format of plugin bundles to package multi-service changes. Describes current limits (few extension points), plans to move cloud providers into plugins in 2021, and that the framework is already in use.
AI-written summary · about
chapters (6)
related talks
43mSpinnaker Plugins: Extending...
32mAccelerating Collaborative Plugin Development
50mSplitting component containers to simplify dependencies
37mA Deep Dive Into OpenSearch Plugin Architecture and Introducing Hot...
06h 54mJetBrains Plugin Developer Conf 2024
40mAMA Spinnaker Roadmap
23mBuild plugins using Pluggy
32mThe HashiCorp Packer Plugin Repository, What’s init?
