docs(secrets): document the plain-IConfigurationRoot reload gap and OtOpcUa's redundant starter (scadaproj#49)

The reload gap for a plain IConfigurationRoot is documented rather than fixed: closing it would mean
inserting a provider into ConfigurationRoot's internal list. No family host is exposed (plain roots
are built with reloadOnChange: false; the rest pass a ConfigurationManager). clustered-secrets.md
notes that AddZbSecretsAkkaReplication now starts the actor itself, so OtOpcUa's
SecretReplicationStarter becomes redundant once it adopts 0.6.6.

Claude-Session: https://claude.ai/code/session_01GT67AEHd2Acv1YPwGfXEoV
This commit is contained in:
Joseph Doherty
2026-11-09 15:23:37 -05:00
parent fac3c5355c
commit db441d9d99
2 changed files with 17 additions and 0 deletions
@@ -154,6 +154,11 @@ Optional but recommended: without it the protocol still round-trips under Akka's
serializer, but the serializer carrying secret ciphertext becomes an inherited default rather than
a deliberate choice.
Since `0.6.6` `AddZbSecretsAkkaReplication` starts the replication actor itself once the host has
started (scadaproj#33), so a node that only expands `${secret:}` references pre-host still
replicates. **OtOpcUa's own `SecretReplicationStarter` is then redundant** — it resolves the same
actor, so keeping it is harmless; drop it when OtOpcUa adopts `0.6.6` (scadaproj#49).
### Securing the transport
Rows on the wire are ciphertext and the KEK never travels, so a passive eavesdropper learns