Cloud Security: document the SBOM route as GET /code/sbom?repo= - #450
Merged
Merged
Conversation
The Code Security SBOM export takes the repository key as a repo query parameter on /code/sbom instead of as a path segment under /code/repos. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
lcbill
approved these changes
Sep 25, 2026
Contributor
Author
|
Self-review (adversarial, from a pristine
|
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.
What
Documents the Code Security SBOM export route in its new form:
GET /code/repos/{repo}/sbomGET /code/sbom?repo=<owner>/<name>(optionalprovider)Updates the route table in
cloud-security/code-security/reference.mdand the Code Security row incloud-security/api-reference.md. The CLI command (limacharlie cloudsec code sbom --repo ...) doesn't change.Compatibility window
The API gateway change behind this route is merged but not yet released to production. Until the next API release, production still serves only the old path, so these two lines describe a route that isn't live yet. The route has no known direct users, so this short window is accepted.
🤖 Generated with Claude Code