Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow retrieving entryIDs or UUIDs via /api/v1/log/entries/retrieve endpoint #859

Merged
merged 4 commits into from
Jun 6, 2022

Conversation

priyawadhwa
Copy link
Contributor

Fixes #855 where only 64 char UUIDs were allowed. Also adds in an integration test.

cc @lkatalin could you take a look at this?

Signed-off-by: Priya Wadhwa priya@chainguard.dev

Summary

Ticket Link

Fixes

Release Note


Fixes a bug where only 64 char UUIDs were allowed. Also adds in an integration test.

Signed-off-by: Priya Wadhwa <priya@chainguard.dev>
@priyawadhwa priyawadhwa requested a review from a team as a code owner June 2, 2022 16:02
@priyawadhwa priyawadhwa requested a review from lkatalin June 2, 2022 16:03
@priyawadhwa priyawadhwa changed the title wip: Allow retrieving entryIDs or UUIDs via /api/v1/log/entries/retrieve endpoint Allow retrieving entryIDs or UUIDs via /api/v1/log/entries/retrieve endpoint Jun 2, 2022
@haydentherapper
Copy link
Contributor

cc @bobcallaway @asraa

asraa
asraa previously approved these changes Jun 2, 2022
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.

Thanks!

dlorenc
dlorenc previously approved these changes Jun 2, 2022
Copy link
Member

@bobcallaway bobcallaway left a comment

Choose a reason for hiding this comment

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

a couple comments

docker-compose.yml Show resolved Hide resolved
openapi.yaml Outdated Show resolved Hide resolved
tests/sharding-e2e-test.sh Outdated Show resolved Hide resolved
Signed-off-by: Priya Wadhwa <priya@chainguard.dev>
@priyawadhwa priyawadhwa dismissed stale reviews from dlorenc and asraa via bbc9906 June 6, 2022 11:06
Signed-off-by: Priya Wadhwa <priya@chainguard.dev>
pkg/sharding/sharding.go Outdated Show resolved Hide resolved
tests/sharding-e2e-test.sh Outdated Show resolved Hide resolved
Signed-off-by: Priya Wadhwa <priya@chainguard.dev>
Copy link
Contributor

@lkatalin lkatalin left a comment

Choose a reason for hiding this comment

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

@priyawadhwa Looks like high level overview is this allows the 80-char entryID for searches in openapi.yaml and then in the search code itself makes sure the treeID is appropriate prepended so the search can be routed correctly?

Not sure why but my searches always worked so I didn't catch that this should also be updated. Thanks for the fix.

@priyawadhwa
Copy link
Contributor Author

@lkatalin yup, this is specifically for the /api/v1/log/entries/retrieve endpoint -- I don't think rekor-cli hits that endpoint except for rekor-cli verify which might be why I didn't notice this in testing.

@dlorenc dlorenc merged commit 143e9ec into sigstore:main Jun 6, 2022
@github-actions github-actions bot added this to the v1.0.0 milestone Jun 6, 2022
@priyawadhwa priyawadhwa deleted the fix-bug branch June 6, 2022 19:09
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.

/api/v1/log/entries/retrieve endpoint does not support the 80 char entryUUID
6 participants