Skip to content
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Commit cec9aab

Browse files
committedFeb 16, 2025·
fixup! rfc: distributed coordinator
update self-references 009->010
1 parent 4573762 commit cec9aab

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed
 

‎rfc/010-distributed-coordinator.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ type Store interface {
4646
Get(key string) ([]byte, error)
4747
Set(key string, value []byte) error
4848
CompareAndSwap(key string, oldVal, newVal []byte) error
49-
Watch(key string, chan<- []byte)) error // <-- New in RFC009.
49+
Watch(key string, chan<- []byte)) error // <-- New in RFC010.
5050
}
5151
```
5252

@@ -149,7 +149,7 @@ For now, the only known role is `coordinator`, but this could be extended in the
149149
type PolicyEntry struct {
150150
SANs []string
151151
WorkloadSecretID string `json:",omitempty"`
152-
Roles []string `json:",omitempty"` // <-- New in RFC009.
152+
Roles []string `json:",omitempty"` // <-- New in RFC010.
153153
}
154154
```
155155

@@ -169,7 +169,7 @@ For each of the ready Coordinators, the recovering Coordinator calls a new `mesh
169169
```proto
170170
service MeshAPI {
171171
rpc NewMeshCert(NewMeshCertRequest) returns (NewMeshCertResponse);
172-
rpc Recover(RecoverRequest) returns (RecoverResponse); // <-- New in RFC009.
172+
rpc Recover(RecoverRequest) returns (RecoverResponse); // <-- New in RFC010.
173173
}
174174
175175
message RecoverRequest {}

0 commit comments

Comments
 (0)
Please sign in to comment.