Configuration
The LittleHorse Quarkus extension uses the same LittleHorse client configuration as other SDKs. You can set LHC_API_HOST, LHC_API_PORT, LHC_TENANT_ID, and other options via environment variables or a properties file.
In addition, the extension supports Quarkus-specific settings for registration behavior.
LittleHorse Client Configuration
The extension configures the gRPC client from the standard LittleHorse environment variables:
| Variable | Description |
|---|---|
LHC_API_HOST | LittleHorse server host (default: localhost) |
LHC_API_PORT | LittleHorse server port (default: 2023) |
LHC_API_PROTOCOL | PLAINTEXT or TLS |
LHC_TENANT_ID | Tenant ID (default: default) |
LHC_CA_CERT | Path to CA cert for TLS |
LHC_CLIENT_CERT | Path to client cert for mTLS |
LHC_CLIENT_KEY | Path to client private key for mTLS |
LHC_OAUTH_CLIENT_ID | OAuth2 client ID |
LHC_OAUTH_CLIENT_SECRET | OAuth2 client secret |
LHC_OAUTH_ACCESS_TOKEN_URL | OAuth2 token URL |
For the full list and details, see Client Configuration.
Extension Configuration
The extension uses the quarkus.littlehorse prefix for its own settings.
Tasks
quarkus.littlehorse.tasks.register.enabled
- Whether to register task definitions at startup.
- Type: boolean
- Default:
true
quarkus.littlehorse.tasks.start.enabled
- Whether to start task workers.
- Type: boolean
- Default:
true
You can override these per task:
quarkus.littlehorse.tasks.my-task.register.enabled=false
quarkus.littlehorse.tasks.my-task.start.enabled=false
Workflows
quarkus.littlehorse.workflows.register.enabled
- Whether to register workflow definitions at startup.
- Type: boolean
- Default:
true
Per-workflow override:
quarkus.littlehorse.workflows.my-workflow.register.enabled=false
User Tasks
quarkus.littlehorse.user-tasks.register.enabled
- Whether to register user task forms at startup.
- Type: boolean
- Default:
true
Structs
quarkus.littlehorse.structs.register.enabled
- Whether to register struct definitions at startup.
- Type: boolean
- Default:
true
quarkus.littlehorse.structs.<struct-name>.register.compatibility
- Schema compatibility when registering structs. See StructDefs and Structs.
- Type: string
- Default:
NO_SCHEMA_UPDATES - Valid values:
NO_SCHEMA_UPDATES,FULLY_COMPATIBLE_SCHEMA_UPDATES(see StructDefCompatibilityType)
RESTful Gateway
When using the RESTful Gateway extension, configure it via application.properties or environment variables. The gateway runs on port 8080 by default (or the Quarkus HTTP port). Swagger UI is available at /q/swagger-ui/ when the application is running.
For OAuth, pass the Bearer token in the Authorization header when calling the gateway.