add API end-points for indexing #1721
Draft
Conversation
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
Signed-off-by: Varsha U N <[email protected]>
|
Hey @AyanSinhaMahapatra , CI tests have failed since I am trying to import |
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.
I built an API to query and download stored package data by implementing a viewset that handles listing, retrieving, and downloading packages by ID, URL, or SHA256 checksum, with filtering capabilities using a dependency for query refinement and read-only access for unauthenticated users. I set up API routing with a dedicated router to manage endpoints under a distinct /api/ path, cleanly separating them from web routes. This enables efficient package reuse, reduces redundant downloads, and enhances ScanCode.io’s functionality with programmatic access to package archives, pending final testing to confirm seamless integration.