Open
Conversation
added 4 commits
April 25, 2023 11:15
Signed-off-by: Blair Drummond <blaird@liatrio.com>
Signed-off-by: Blair Drummond <blaird@liatrio.com>
Signed-off-by: Blair Drummond <blaird@liatrio.com>
Signed-off-by: Blair Drummond <blaird@liatrio.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
By default
rekor-sidekickfollows the tail of the Rekor log. This probably makes sense in most use-cases, but if we're mirroring attestations out to a searchable database, or testing on a self-hosted Rekor instance (which is receiving less traffic) it's helpful to be able to replay the whole Rekor instance or replay it from a certain point.The new
indexconfiguration, when set to-1(default) just follows the Rekor instance like before, but if you set it to a value >=0, then it replays rekor from that index.go test ./...)