OmniRoute/changelog.d/features/11906-omniroute-plugins-dir.md at 0d0aaaf0aa03e74499c8809b8bc274beffc2db63

mirror of https://github.com/diegosouzapw/OmniRoute.git synced 2026-09-21 14:22:14 +03:00

Files

Paco Cartones 2471a0d95e feat(plugins): add OMNIROUTE_PLUGINS_DIR to override the plugin scan directory (#11827 ) (#11906 )

Boarded with 8 other PRs in one combined worktree: typecheck:core, check:file-size, check:changelog-integrity, check:complexity, check:cognitive-complexity, check:cycles, check-native-deps all green; 75/75 focused tests pass. Clean, well-scoped env-override with correct blank-value handling and a startup log naming the resolution source. Thanks.

2026-08-30 05:28:29 -03:00

758 B

Raw Blame History

feat(plugins): OMNIROUTE_PLUGINS_DIR sets the directory the runtime plugin scanner reads — and the root the plugin manager installs into — overriding the HOME-derived default, so a Docker/K8s deployment can point straight at its bind-mounted plugin tree instead of moving HOME just to relocate the scan path. An image that exports no home no longer scans /tmp/.omniroute/plugins in silence: the resolved directory is logged once at startup as scanner.dir_resolved, naming the input that won. Unset, behaviour is unchanged. Distinct from the CLI-only OMNIROUTE_PLUGIN_PATH, which finds omniroute-cmd-* command packages and never reached this scanner (#11906) — thanks @amaleta

758 B Raw Blame History

758 B

Raw Blame History