-
- Downloads
Require tlog_id when inactive shard config file is passed in (#739)
tlog_id specifes the active shard and is kept for backwards compatibility.
To avoid replicating information, the shard config file is used only to
specify inactive shards and must be used in conjunction with a tlog_id flag.
Together, these build the logRanges type in the sharding module.
Signed-off-by:
Lily Sturmann <lsturman@redhat.com>
Showing
- cmd/rekor-server/app/serve.go 1 addition, 1 deletioncmd/rekor-server/app/serve.go
- pkg/api/api.go 1 addition, 2 deletionspkg/api/api.go
- pkg/api/tlog.go 1 addition, 1 deletionpkg/api/tlog.go
- pkg/sharding/log_index.go 15 additions, 5 deletionspkg/sharding/log_index.go
- pkg/sharding/log_index_test.go 18 additions, 24 deletionspkg/sharding/log_index_test.go
- pkg/sharding/ranges.go 33 additions, 25 deletionspkg/sharding/ranges.go
- pkg/sharding/ranges_test.go 9 additions, 12 deletionspkg/sharding/ranges_test.go
Loading
Please register or sign in to comment