configDumpLines
configDumpLines(
config):string
Defined in: src/diagnostics/ConfigDump.ts:241
The boot dump actor-ts.diagnostics.log-config-on-start turns on, as the
one string it is logged as (#867).
One record, not one per key. A merged tree is a few hundred leaves;
that many records buries whatever else the log was saying and gives a
structured backend a few hundred rows with nothing to correlate them by.
Newlines inside one message survive both shipped loggers — ConsoleLogger
writes the string, JsonLogger escapes it into the msg field — so the
dump reaches a log aggregator as a single searchable event.
Values are JSON-encoded, and that is a guard rather than a formatting
choice. A config value can contain a newline — application.conf may
quote one, and ${?SOMETHING} can substitute one out of the environment —
and an un-encoded value could then forge lines into the dump it is part of.
JSON.stringify escapes them, and it renders a list as a list instead of
flattening the one shape an operator most needs to read. A key gets the
same treatment for the same reason: a quoted HOCON key may hold an escaped
newline too, so a key that is not a bare one prints quoted, escapes and all
— see pathOf.
The header states what the body cannot: how many keys were withheld, and why — their name, the secrets file holding them, or the variable that supplied them — how many of the lists it does print had a credential field withheld, how many of the values it does print had a URL’s credentials masked, the active profile, the four files it looked for and whether each was there, and whether the layer column is an answer or the unattributed fallback. A line names the variables behind its value, withheld or not: “why is this not what my file says” is as often an exported variable as a layer.
Parameters
Section titled “Parameters”config
Section titled “config”Returns
Section titled “Returns”string
