consul

Commit Graph

Author	SHA1	Message	Date
freddygv	c04515a844	Use proto message for each secrets write op Previously there was a field indicating the operation that triggered a secrets write. Now there is a message for each operation and it contains the secret ID being persisted.	2022-08-08 01:41:00 -06:00
freddygv	60d6e28c97	Pass explicit signal with op for secrets write Previously the updates to the peering secrets UUID table relied on inferring what action triggered the update based on a reconciliation against the existing secrets. Instead we now explicitly require the operation to be given so that the inference isn't necessary. This makes the UUID table logic easier to reason about and fixes some related bugs. There is also an update so that the peering secrets get handled on snapshots/restores.	2022-08-03 17:25:12 -05:00
Matt Keeler	f74d0cef7a	Implement/Utilize secrets for Peering Replication Stream (#13977 )	2022-08-01 10:33:18 -04:00

Author

SHA1

Message

Date

freddygv

c04515a844

Use proto message for each secrets write op

Previously there was a field indicating the operation that triggered a
secrets write. Now there is a message for each operation and it contains
the secret ID being persisted.

2022-08-08 01:41:00 -06:00

freddygv

60d6e28c97

Pass explicit signal with op for secrets write

Previously the updates to the peering secrets UUID table relied on
inferring what action triggered the update based on a reconciliation
against the existing secrets.

Instead we now explicitly require the operation to be given so that the
inference isn't necessary. This makes the UUID table logic easier to
reason about and fixes some related bugs.

There is also an update so that the peering secrets get handled on
snapshots/restores.

2022-08-03 17:25:12 -05:00

Matt Keeler

f74d0cef7a

Implement/Utilize secrets for Peering Replication Stream (#13977 )

2022-08-01 10:33:18 -04:00

3 Commits (325d0e2320246859df93df7a30b69d6582e20170)