OSS server: logs and default toolsets rejected as 'does not exist'

[wjf3121]

Bug

When configuring HARNESS_TOOLSETS=default,pipelines,logs, the logs and default toolsets are rejected during startup with:

level=WARN msg="Toolset denied" toolset=logs reason="toolset does not exist"
level=WARN msg="Toolset denied" toolset=default reason="toolset does not exist"

Only pipelines is accepted.

Root Cause

In pkg/modules/module_registry.go, NewModuleRegistry uses commonModules.NewCoreModule(config, tsg) to build the registry. The common CoreModule.Toolsets() does not include "logs" in its return value.

The ExtendedCoreModule in pkg/modules/core.go was written specifically to add "logs" to the toolset list, but it is never used in the registry. When ValidateToolsets runs, it cannot find "logs" in any module's toolset list and rejects it.

Fix

One-line change in pkg/modules/module_registry.go:

-			commonModules.NewCoreModule(config, tsg),
+			NewExtendedCoreModule(config, tsg),

This makes the registry use the extended module that includes "logs" in its Toolsets() return value, so license validation recognizes it.

Environment

• OSS harness-mcp-server built from source (latest main)
• Version: 0.1.0

[thisrohangupta]

Thank you for reaching out I have filed the internal Kira and we will get back to you shortly