-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
Fully Compatible
-
CAR Team 2026-03-02, CAR Team 2026-03-16
-
2
-
🟩 Routing and Topology
-
None
-
None
-
None
-
None
-
None
-
None
Moving from the POC in this PR we need to create a proper infrastructure for the plugin. The infrastructure should include just:
- registering method for the plugins
- one sample API (e.g. upgradeMetadata/downgradeMetadata) with the required machinery to call the corresponding functions in the plugins
- interface to be implemented for the plugins (with empty defaults, so that a plugin can just implement what it needs)
- a proper directory structure for the plugins
We want to keep the skeleton simple, and add the infrastructure functionality as part of the other tickets rather than loading this ticket with all of them. This will help keep the infrastructure light, at the cost of possibly having to redo some of the work.
- related to
-
SERVER-120553 Migrate the legacy upgrade/downgrade code to an FCV step plugin
-
- In Code Review
-
-
SERVER-117035 Proof of concept of a plugin system for FCV upgrade/downgrade steps
-
- Closed
-