docs(secrets): 0.6.3 changelog entry
This commit is contained in:
@@ -5,6 +5,27 @@ follows [Keep a Changelog](https://keepachangelog.com/); versions are shared acr
|
||||
package in the family (see `Directory.Build.props`) even when a given release only touches
|
||||
one of them.
|
||||
|
||||
## 0.6.3 — 2026-09-28
|
||||
|
||||
### Added
|
||||
|
||||
- **gRPC hub follower sweeps are observable.** `GrpcSecretSyncService` (package
|
||||
`ZB.MOM.WW.Secrets.Replicator.Grpc`) now logs every sweep outcome instead of only the sweeps
|
||||
that pull a change:
|
||||
- `EventId 4` (Debug) — a sweep found nothing new; logged on every in-sync sweep.
|
||||
- `EventId 5` (Information) — an in-sync heartbeat, at most once per
|
||||
`SecretsGrpcHubClientOptions.InSyncLogInterval` (new, default 1 hour, validated positive), so
|
||||
"the loop is alive and still agrees with the hub" is visible at the default log level without
|
||||
a line every 30 seconds.
|
||||
- `EventId 6` (Information) — the first successful sweep after one or more failures, naming
|
||||
the failure count.
|
||||
- **`ISecretsHubSyncStatus`** — a public, DI-registered read model of the follower loop:
|
||||
`LastSweepUtc`, `LastSuccessUtc`, `ConsecutiveFailures`, `LastError`. Getters are synchronized
|
||||
with the writer, so a health check or status page reads a consistent snapshot.
|
||||
|
||||
No behaviour change to syncing itself, and no wire or schema change. Only hub followers gain
|
||||
anything from this release; other consumers can stay on 0.6.2.
|
||||
|
||||
## 0.6.2 — 2026-08-11
|
||||
|
||||
### Changed
|
||||
|
||||
Reference in New Issue
Block a user