Configuration Properties
Status: Version-sensitive reference aligned with teaql-java
1.525-RELEASE. The current modular runtime does not expose the two legacy
Spring property bindings previously presented here as current properties.
| Metadata | Value |
|---|---|
| Authority | teaql-java 1.525-RELEASE source, generated Java output, and installed artifacts. |
| Scope | Modular Java runtime, optional runtime-log module, datasource boundary, and client configuration. |
| Verified version | teaql-java 1.525-RELEASE from the official version endpoint on 2026-07-13. |
| Verification | Inspect runtime configuration binding or auto-configuration source, then run the affected application path. |
| Update trigger | Configuration binding, default, startup behavior, or runtime-module change. |
Current Java 1.525 Runtime Boundary
The 1.525-RELEASE modular runtime creates contexts through
TeaQLUserContextFactory and Java ServiceLoader implementations of
ContextAssembler. It does not bind teaql.contextClass. Register the project
assembler through META-INF/services/io.teaql.core.spi.ContextAssembler (or
the Java module service declaration) instead of relying on that legacy key.
Schema support is an explicit SchemaExecutor.ensureSchema(UserContext)
capability implemented by selected database executors. No
teaql.ensureSchema binding exists in the 1.525-RELEASE source. Invoke schema
work at a controlled setup/admin boundary and do not infer migration policy or
startup behavior from the legacy property name.
Legacy Spring Property Names
teaql.contextClass and teaql.ensureSchema may still exist in older Spring
Boot starter lines. They are retained in older application documentation only
as migration clues, not as current 1.525-RELEASE configuration. Verify the
exact starter artifact and its configuration metadata before using either key.
Optional Java Runtime Log Module
The teaql-runtime-log module reads TEAQL_* Java system properties first,
then environment variables. Values are cached at class initialization and are
not dynamically reloaded.
| Name | Type/values | Verified default |
|---|---|---|
TEAQL_LOG_FORMAT | human, json, or debug | human |
TEAQL_AUDIT_LOG | _silent, _summary, _full, _full_with_payload | _full |
TEAQL_SQL_LOG | Same levels | _summary |
TEAQL_TOOL_LOG | Same levels | _full |
TEAQL_AUDIT_LOG_ENTITIES | Comma-separated entity names | No filter |
TEAQL_SQL_LOG_TABLES | Comma-separated table substrings | No filter |
TEAQL_TOOL_LOG_FOCUS | Comma-separated tool module names | No filter |
TEAQL_LOG_ENDPOINT | stdout, guarded off, or a file path | TEAQL_DOMAIN.log, otherwise executable-name .log |
TEAQL_LOG_MAX_SIZE | Bytes or integer plus K/KB, M/MB, G/GB | 50MB |
TEAQL_LOG_MAX_FILES | Integer | 7 |
Invalid log levels, sizes, and file counts fall back to their defaults. Empty
filter values mean no filter. TEAQL_TRACE_MODE=off is ignored unless the
runtime's explicit extreme-test acknowledgement is also present; disabling
trace is not a normal production optimization.
Datasource Configuration Boundary
Database URLs, credentials, pools, and driver settings may be provided by the
host framework or provider rather than a universal teaql.datasource.*
namespace. Use the configuration contract of the selected Spring Boot, Quarkus,
Micronaut, JDBC, or provider integration.
The earlier generic teaql.datasource.url example has been removed because no
authoritative binding or default was identified in this repository.
Rust Configuration Boundary
The current documentation provides environment-driven Rust runtime settings,
not an authoritative universal teaql.toml schema. See
Environment Variables.
Cargo Client Configuration File
cargo-teaql 2.0.8 reads ~/.teaql/config.yml with these keys:
| Key | Type | Built-in default |
|---|---|---|
endpoint_prefix | URL string | https://api.teaql.io/latest/ |
api_key | Optional string | Built-in free-tier credential. |
build_dir | Path | build |
timeout_seconds | Positive integer seconds | 1200 |
Use environment variables or CI secret injection for dedicated API keys.
show-config serializes the stored YAML, so redact its output before sharing.
Client precedence and Maven equivalents are listed in
Environment Variables and
Client Tools Cheat Sheet.
Remaining Catalog Work
Before this page can be called complete, maintainers must extract and verify:
- publish configuration metadata for any new Spring integration artifact;
- document provider-specific datasource and pool settings;
- define removal and deprecation policy for legacy Spring keys;
- verify runtime-log behavior from the released artifact in an executable Java golden path.