consul/agent/grpc-external/services/peerstream
freddygv 1031ffc3c7 Re-validate existing secrets at state store
Previously establishment and pending secrets were only checked at the
RPC layer. However, given that these are Check-and-Set transactions we
should ensure that the given secrets are still valid when persisting a
secret exchange or promotion.

Otherwise it would be possible for concurrent requests to overwrite each
other.
2022-08-08 09:06:07 -06:00
..
health_snapshot.go Remove duplicate comment 2022-07-26 10:19:49 -07:00
health_snapshot_test.go Use Node Name for peering healthSnapshot instead of ID (#13773) 2022-07-15 10:51:38 -04:00
mock_ACLResolver.go
replication.go peering: refactor reconcile, cleanup (#13795) 2022-07-19 11:43:29 -07:00
server.go Use proto message for each secrets write op 2022-08-08 01:41:00 -06:00
server_test.go Use proto message for each secrets write op 2022-08-08 01:41:00 -06:00
stream_resources.go Re-validate existing secrets at state store 2022-08-08 09:06:07 -06:00
stream_test.go Re-validate existing secrets at state store 2022-08-08 09:06:07 -06:00
stream_tracker.go Rename receive to recv in tracker (#13896) 2022-07-25 16:08:03 -07:00
stream_tracker_test.go peering: read endpoints can now return failing status (#13849) 2022-07-25 14:27:53 -07:00
subscription_blocking.go peerstream: require a resource subscription to receive updates of that type (#13767) 2022-07-15 15:03:40 -05:00
subscription_manager.go peerstream: require a resource subscription to receive updates of that type (#13767) 2022-07-15 15:03:40 -05:00
subscription_manager_test.go Implement/Utilize secrets for Peering Replication Stream (#13977) 2022-08-01 10:33:18 -04:00
subscription_state.go
subscription_state_test.go
subscription_view.go
subscription_view_test.go
testing.go peerstream: require a resource subscription to receive updates of that type (#13767) 2022-07-15 15:03:40 -05:00