Configuration on NOCFoundry Docs

Tool Catalogs

Mon, 01 Jan 0001 00:00:00 +0000

Tool Catalogs

Tool catalogs define the operational resources NOCFoundry loads at startup.

Supported catalog flags

--tools-file
--tools-files
--tools-folder
--prebuilt

These are mutually exclusive where appropriate:

--tools-file, --tools-files, and --tools-folder cannot be combined
--prebuilt can be combined with custom tool catalogs when you want bundled capabilities plus your own configs

What a catalog can contain

Tool catalogs can define:

sources
device groups
auth services
tools
toolsets
prompts
promptsets
embedding models

Prebuilt catalogs

--prebuilt takes a bundled catalog name, not an individual tool name.

Server Config

Mon, 01 Jan 0001 00:00:00 +0000

Server Config

--server-config carries server-wide runtime policy that should not be owned by individual tool catalog files.

Current focus

Today, the most important server config capabilities are:

endpoint auth for /api
endpoint auth for /mcp
browser UI auth configuration for PKCE login

Example

auth:
 endpointAuth:
 api:
 enabled: true
 authServices: ["noc-keycloak"]
 audience: ${NOCFOUNDRY_BASE_URL:http://127.0.0.1:5000}/api
 mcp:
 enabled: true
 authServices: ["noc-keycloak"]
 audience: ${NOCFOUNDRY_BASE_URL:http://127.0.0.1:5000}/mcp
 ui:
 enabled: true
 authService: noc-keycloak
 clientId: ${KEYCLOAK_UI_CLIENT_ID:noc-foundry-ui}
 scopes: ["openid", "profile", "email"]
 redirectPath: /ui/auth/callback

Rules to remember

endpoint auth policy is global to the server, not per tool catalog
auth services are still defined in tool catalogs and referenced here by name
UI login depends on API endpoint auth being enabled

Start command

./nocfoundry \
 --tools-file examples/tools-configs/keycloak-protected-validation.yaml \
 --server-config examples/server-configs/protected-api-mcp-ui.yaml \
 --validation-config examples/validation-runtime-configs/durable-validation-sqlite.yaml \
 --ui

Validation Runtime

Mon, 01 Jan 0001 00:00:00 +0000

Validation Runtime

--validation-config controls how validation runs are executed and stored.

Key runtime settings

executionBackend
storeBackend
sqlitePath
durableTaskSQLitePath
maxConcurrentRuns
maxConcurrentSteps
resultRetention
eventRetention

Example

executionBackend: durabletask
storeBackend: sqlite
sqlitePath: /var/lib/nocfoundry/noc-foundry-validation-runs.sqlite
durableTaskSQLitePath: /var/lib/nocfoundry/noc-foundry-validation-taskhub.sqlite
maxConcurrentRuns: 4
maxConcurrentSteps: 4
resultRetention: 24h
eventRetention: 24h

Backend choices

local is simpler and good for lightweight execution
durabletask is better for long-running validations that should survive interruption

Store choices

memory is ephemeral
sqlite provides persistence for status, results, and events

Recommended local lab setup

For the protected validation example, use: