Honeydipper supports loading remote drivers by acquiring binaries at runtime, verifying integrity, and executing from a local cache.
This guide explains how to configure:
drivers.daemon.registry, direct, and local sources.Current behavior:
ed25519 (publicKey + signature).version or channel.drivers.daemon.registries.builtin.registry allowed by default.direct denied by default.local denied by default.drivers.daemon.registries.drivers.daemon.drivers.<driverName>.handlerData.registry to reference a named registry.drivers.daemon.featureMap.Example:
---
drivers:
daemon:
registries:
github-public:
baseURL: https://example.com/driver-registry
requireSignature: true
publicKey: <base64-ed25519-public-key>
Notes:
baseURL is accepted and normalized to registryURL during resolution.registryURL can also be used directly in registry definitions.builtin cannot be defined in config.---
drivers:
daemon:
drivers:
custom-webhook:
name: custom-webhook
type: remote
handlerData:
registry: github-public
channel: stable
# optional: version: 1.2.3
Resolution order:
version is set, that version is used.channel is used (default: stable).latest is used.Direct URL is supported but denied by default by source policy.
---
drivers:
daemon:
remoteDriverPolicy:
direct:
enabled: true
drivers:
custom-direct:
name: custom-direct
type: remote
handlerData:
url: https://example.com/bin/custom-direct-linux-amd64
sha256: <sha256-hex>
fileName: custom-direct
requireSignature: true
publicKey: <base64-ed25519-public-key>
signature: <base64-ed25519-signature>
Local source is also denied by default.
---
drivers:
daemon:
remoteDriverPolicy:
local:
enabled: true
drivers:
custom-local:
name: custom-local
type: remote
handlerData:
localPath: /opt/honeydipper/drivers/local/custom-local
Configure under drivers.daemon.remoteDriverPolicy:
---
drivers:
daemon:
remoteDriverPolicy:
registry:
enabled: true
direct:
enabled: false
local:
enabled: false
Defaults when policy is not set:
registry.enabled = truedirect.enabled = falselocal.enabled = falseSignature verification fields can come from:
handlerData directly.Fields:
requireSignature (bool)publicKey (base64 ed25519 public key)signature (base64 signature over artifact digest bytes)Global strict mode can be enabled with environment variable:
HONEYDIPPER_REMOTE_REQUIRE_SIGNATURE=true
Each driver is resolved from <registryURL>/<driverName>.json.
Example:
{
"driver": "custom-webhook",
"latest": "1.2.3",
"publicKey": "<base64-ed25519-public-key>",
"channels": {
"stable": "1.2.3",
"canary": "1.3.0-rc1"
},
"versions": {
"1.2.3": {
"publicKey": "<optional-version-level-key>",
"artifacts": [
{
"os": "linux",
"arch": "amd64",
"url": "https://example.com/bin/custom-webhook-linux-amd64",
"sha256": "<sha256-hex>",
"fileName": "custom-webhook",
"publicKey": "<optional-artifact-level-key>",
"signature": "<base64-ed25519-signature>"
}
]
}
}
}
Remote drivers are stored in a cache directory structure organized by their SHA-256 digest:
<remotePath>/sha256/<sha256-driver-digest>/
└── <fileName>
Where:
<remotePath> is the root cache directory (defaults to /opt/honeydipper/drivers/cache)<sha256-driver-digest> is the hex-encoded SHA-256 hash of the driver binary<fileName> is the name of the driver executableThe remote path can be configured using the HONEYDIPPER_DRIVERS_CACHE environment variable.
Example directory structure:
/opt/honeydipper/drivers/cache/sha256/
└── a1b2c3d4e5f6.../
└── custom-webhook-linux-amd64
To prevent concurrent downloads of the same driver, Honeydipper uses a directory-based mutex mechanism. A lock is acquired by creating a directory named after the driver’s SHA-256 digest. If the directory already exists, the process waits for the lock to be released (with a default timeout of 30 seconds).
If the timeout is exceeded, the acquisition fails with a timeout error.
Honeydipper can automatically install required system packages before launching a remote driver. This is useful when a remote driver has dependencies on system libraries or tools.
To enable package installation, add a requiredPackages section to the driver’s handlerData:
---
drivers:
daemon:
drivers:
custom-driver:
name: custom-driver
type: remote
handlerData:
registry: github-public
requiredPackages:
apk:
- libssl1.1
- curl
apt:
- libssl1.1
- curl
dnf:
- openssl
- curl
brew:
- openssl
Package managers are auto-detected based on the host OS:
apk: Alpine Linuxapt: Debian/Ubuntudnf: Fedora/RHELbrew: macOSIf the detected package manager is not listed in requiredPackages, the driver will fail to start with an error.
/opt/honeydipper/drivers/cache.HONEYDIPPER_DRIVERS_CACHE to change cache location.Common failures:
remote driver source is not allowed by policy: direct
drivers.daemon.remoteDriverPolicy.direct.enabled.builtin remote registry cannot be overridden
drivers.daemon.registries.builtin from config.failed resolving remote driver version from registry
version, channel, and manifest versions content.timeout waiting for cache lock
requiredPackages does not define packages for detected package manager
apk, apt, dnf, or brew) to the requiredPackages section.Deferred enhancements: