You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs: improve plugin development path structure guidance
- Use ./local/lib/python3/cmk as primary directory structure
- Add critical warning about check_mk symlink to prevent production issues
- Change all development paths from ~/local to ./local (OMD sites still use ~/local)
- Fix checkman location to be inside plugin-specific directory
- Update package distribution to reference mkp-builder from GitHub
- Remove manual package creation in favor of mkp-builder tool
This change prevents accidental overwriting of symlinks in production
installations and provides clearer guidance for development environments.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: CHANGES.md
+6-1Lines changed: 6 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,14 +14,19 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
14
14
- Reorganized cmk-plugin-guide.md structure with table of contents and improved flow
15
15
- Clarified SimpleLevels documentation to remove confusion about parameter formats
16
16
- Added "Common Pitfalls and Solutions" section to cmk-plugin-guide.md
17
-
- Added note about check_mk → python3/cmk symlink relationship to avoid path confusion
17
+
-**IMPORTANT**: Updated directory structure guidance to use `./local/lib/python3/cmk` as primary path with `./local/lib/check_mk` as symlink to prevent production issues
18
+
- Changed all path examples from `~/local/` to `./local/` for development checkouts (OMD sites still use `~/local/`)
19
+
- Updated package distribution section to reference mkp-builder from GitHub (oposs/mkp-builder)
20
+
- Fixed checkman directory location to be inside plugin-specific folder structure
21
+
- Removed manual package creation instructions in favor of mkp-builder tool
18
22
19
23
### Fixed
20
24
- Fixed critical typos in cmk-plugin-guide.md (`cmk.base.pyugins` → `cmk.base.plugins`)
21
25
- Corrected bakery plugin directory paths for consistency
22
26
- Fixed missing `parameter_form=` in ruleset example code
23
27
- Fixed temperature monitor example to use correct `HostAndItemCondition`
24
28
- Removed redundant and contradictory information about SimpleLevels handling
> **📝 Important Path Note**: In CheckMK, `~/local/lib/check_mk` is a symlink to `~/local/lib/python3/cmk`. You may encounter both paths in documentation, error messages, and examples - they refer to the same location. This can cause confusion when debugging path-related issues or following different documentation sources.
59
+
> **⚠️ Critical Path Setup**:
60
+
> -**Always use `./local/lib/python3/cmk` as the actual directory**
61
+
> - Create `./local/lib/check_mk` as a symlink pointing to `./local/lib/python3/cmk`
62
+
> - This prevents accidentally overwriting the symlink in production installations
63
+
> - In a CheckMK OMD site, paths start with `~/local/` (site user's home)
64
+
> - In regular development checkouts, use `./local/` (relative to project root)
65
+
>
66
+
> ```bash
67
+
># Setup correct structure in development
68
+
> mkdir -p ./local/lib/python3/cmk
69
+
> ln -s python3/cmk ./local/lib/check_mk
70
+
>```
71
+
72
+
For a real-world example structure, see: https://github.com/oposs/cmk-oposs_smart_error
0 commit comments