-
Notifications
You must be signed in to change notification settings - Fork 168
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
Conversation
Fixes a bug where only 64 char UUIDs were allowed. Also adds in an integration test. Signed-off-by: Priya Wadhwa <priya@chainguard.dev>
/api/v1/log/entries/retrieve
endpoint/api/v1/log/entries/retrieve
endpoint
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
a couple comments
Signed-off-by: Priya Wadhwa <priya@chainguard.dev>
Signed-off-by: Priya Wadhwa <priya@chainguard.dev>
There was a problem hiding this 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.
@lkatalin yup, this is specifically for the |
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