Werk #14719: Local customizations might need adjustment due refactorings in GUI code (PasswordFromStore)
| Component | Setup | ||||||
| Title | Local customizations might need adjustment due refactorings in GUI code (PasswordFromStore) | ||||||
| Date | Sep 2, 2022 | ||||||
| Level | Trivial Change | ||||||
| Class | New Feature | ||||||
| Compatibility | Incompatible - Manual interaction might be required | ||||||
| Checkmk versions & editions |
|
This werk only affects users of non-Checkmk local customizations (single files and MKPs from non- Checkmk sources such as the Checkmk exchange).
Before this werk, the Checkmk codebase offered two convenience functions for creating ValueSpecs for passwords (either entered directly or selected from the password store): IndividualOrStoredPassword and PasswordFromStore. These two functions had misleading names and were therefore renamed:
- IndividualOrStoredPassword was renamed to MigrateToIndividualOrStoredPassword, because this actually reflects what the returned ValueSpec does: It allows users to either directly enter a password or select one from the store. Furthermore, it also handles legacy configurations which did not offer the option to use the password store.
- PasswordFromStore was renamed to IndividualOrStoredPassword, which also reflects its purpose: either directly enter a password or to select one from the store, but without the handling of legacy configurations.
To stay compatible, we recommend to simply use IndividualOrStoredPassword instead of PasswordFromStore in Checkmk 2.1 customizations, which will continue working when upgrading to 2.2.
Note that this only affects non-Checkmk customizations because as of the writing of this werk, any customization produced by Checkmk will be obsolete with Checkmk 2.2.