Where lumnik stands
beta. Nobody outside the lumnik team has run lumnik in production yet.
What each release adds: the release notes.
What is deliberately not there
Each line is a decision, declared on the page of its surface and gathered here.
| Surface | What is not there | Declared in |
|---|---|---|
| GraphQL | mutations, subscriptions, schema-introspection discovery, persisted queries, query batching, per-endpoint header overrides, on_error: warn |
GraphQL — Not yet supported |
| REST | mode: api_cursor — accepted with a warning, and run as full. Per-endpoint headers — declare them once, at spec.headers |
REST |
| SOAP | SOAP 1.1 envelopes only — a service that requires SOAP 1.2 (application/soap+xml) cannot be read |
SOAP |
| Kafka (Pro) | JSON only — no Avro, Protobuf or Schema Registry; one topic per connector, no filtering by key or header; no mapping block, so no hooks at ingestion; no pre-flight test; SASL/SCRAM, mTLS and OAuth | Kafka — Limitations |
| Transformers | validate-row after split-row, and aggregator on a csv-file run — both refused at lm apply, with the arithmetic reason |
Transformers |
| Events | a Process does not evaluate rows that existed before it was applied: only later inserts and source changes fire it | How lumnik breathes |
| Chat | declared status aliases feed the dormancy watch and the chat's background knowledge, not the chat's SQL or a view's filters — the chat matches the literal values in the column | How lumnik breathes |
| Workflows | the transition journal is kept until lm workflow rm. Each dormancy check (every 15 minutes by default) reads the whole watched table |
Workflows |
| Exports | CSV only, one entity per export, mode: snapshot only (no delta, no resume); SFTP and S3 only; four formatters, a row filter with equals/in only; no back-fill of missed slots, no automatic retry |
Exports — Not in this version |
| Search | a row deleted outside ingestion (a DELETE in the database, lm endpoint purge) stays searchable until the index is rebuilt |
SearchIndex — Rows deleted directly in the database |
| SCIM (Pro) | no /Groups; no bulk, sorting, etags or changePassword; no pagination beyond the two eq filters; not the full PATCH path grammar; no /Schemas or /ResourceTypes |
SCIM — Not supported |
| Identity | SAML-only IdPs are not supported by direct trust — front them with a broker and point lumnik at the broker | Bring your own IdP |
| Encryption | rotating the master key. Rotating one secret's value is supported: lm secret list shows it under ROTATED_AT |
RLS and encryption |
Kafka and SCIM are in the Pro build only: see The two editions.
What is not finished
Nothing known today. A defect found from here on is listed here until it is fixed.
When beta goes away
When someone outside the lumnik team has run lumnik in production, with this list still empty. To be that first outside run, start with the guided path.
See also
- The two editions — what each build contains
- Guided path — the three half-days
- How lumnik works — the mechanism behind all of it