Skip to content

output log information#93

Open
lumjjb wants to merge 2 commits intoslsa-framework:mainfrom
lumjjb:add-log-output
Open

output log information#93
lumjjb wants to merge 2 commits intoslsa-framework:mainfrom
lumjjb:add-log-output

Conversation

@lumjjb
Copy link
Contributor

@lumjjb lumjjb commented Apr 29, 2022

Signed-off-by: Brandon Lum lumjjb@gmail.com

Copy link
Contributor

@asraa asraa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some small feedback -- the log UUID can suffice to determine the shard and entry (see sigstore/rekor#587), so if you want, you can return the UUID as a single reference to the entry rather than log-index and shard (log ID)

WDYT?

@lumjjb
Copy link
Contributor Author

lumjjb commented Apr 29, 2022

hmm, i could have missed something but didn't see the UUID as part of the LogEntryAnon struct

@lumjjb lumjjb force-pushed the add-log-output branch from 474670c to 15d1deb Compare May 2, 2022 16:53
lumjjb added 2 commits May 2, 2022 12:54
Signed-off-by: Brandon Lum <lumjjb@gmail.com>
Signed-off-by: Brandon Lum <lumjjb@gmail.com>
@lumjjb lumjjb force-pushed the add-log-output branch from 15d1deb to 4a8aae9 Compare May 2, 2022 17:02
@lumjjb lumjjb marked this pull request as ready for review May 2, 2022 19:17
@lumjjb lumjjb changed the title DNM: output log information output log information May 2, 2022
@asraa
Copy link
Contributor

asraa commented May 5, 2022

Could you please merge or rebase? I'll take a re-review!

I think from what I read - sharding is currently changing, but the log-index is indeed unique enough to determine the shard (log-index should be sum(inactive shards) + active shard), so you can compute where you are given the log ranges

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants