Werk #14821: Custom extensions might need adjustment due refactorings in GUI code (Transform)
|Title||Custom extensions might need adjustment due refactorings in GUI code (<tt>Transform</tt>)|
|Date||Sep 6, 2022|
|Checkmk Editon||Checkmk Raw (CRE)|
|Compatibility||Incompatible - Manual interaction might be required|
This werk only affects users of non-tribe29 custom extensions (single files and MKPs from non- tribe29 sources such as the Checkmk exchange).
Before this werk, the Checkmk codebase offered the ValueSpec subclass Transform, which was used for two things:
- Changing the format in which configured values are stored (back and forth
- Updating legacy configurations to the current format (forth only specified).
As of this werk, the Transform class can only be used for the first point above (changing the storage format). It now expects two mandatory arguments into_vs (previously forth) and out_of_vs (previously back).
For updating legacy configurations, use the new Migrate class, which requires a mandatory migrate argument. This is the equivalent of specifying forth only in the old Transform class.