nodes/src/nodes/store_weaviate/services.json sets the node's connection profile twice, to different values.
Parsed from develop @ b8068d7:
preconfig.default : "cloud"
weaviate.profile.default : "local"
Both describe the same choice — whether the node talks to a Weaviate Cloud cluster or a local instance — so which one takes effect depends on whether the profile arrives through preconfig or falls through to the field default.
Why it matters
The two branches are not interchangeable. cloud and local differ in host, port, and authentication, so a user who lands on the wrong one gets a connection failure whose cause is not visible from the node's own documentation — the README correctly reports local, because that is what weaviate.profile.default says, while the preconfig path says otherwise.
Fix
Decide which is correct for a fresh node, set both to it, then re-run nodes:docs-generate so the README follows. I did not pick one: it is a behaviour decision for whoever owns this node, not something to settle from the schema alone.
Provenance
Surfaced by CodeRabbit during review of #1773 (a docs regeneration PR). Filing it here rather than fixing it there, since changing a connection default is a functional change and would have been buried in a diff of 25 regenerated files. The generated table in that PR is faithful to the schema; the schema is what disagrees with itself.
nodes/src/nodes/store_weaviate/services.jsonsets the node's connection profile twice, to different values.Parsed from
develop@b8068d7:Both describe the same choice — whether the node talks to a Weaviate Cloud cluster or a local instance — so which one takes effect depends on whether the profile arrives through preconfig or falls through to the field default.
Why it matters
The two branches are not interchangeable.
cloudandlocaldiffer in host, port, and authentication, so a user who lands on the wrong one gets a connection failure whose cause is not visible from the node's own documentation — the README correctly reportslocal, because that is whatweaviate.profile.defaultsays, while the preconfig path says otherwise.Fix
Decide which is correct for a fresh node, set both to it, then re-run
nodes:docs-generateso the README follows. I did not pick one: it is a behaviour decision for whoever owns this node, not something to settle from the schema alone.Provenance
Surfaced by CodeRabbit during review of #1773 (a docs regeneration PR). Filing it here rather than fixing it there, since changing a connection default is a functional change and would have been buried in a diff of 25 regenerated files. The generated table in that PR is faithful to the schema; the schema is what disagrees with itself.