cloudsec: code ingest no longer requires a collected repository - #342
Merged
Conversation
Documentation only — the wire contract is unchanged, so `limacharlie cloudsec code ingest` needed no code change. What did change is the backend: a push for a repository no connected source-control organization covers now CREATES the repository rather than being refused with repo_not_in_inventory, and both the CLI help and the SDK docstring told customers the opposite. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
lcbill
previously approved these changes
Aug 27, 2026
…ult branch
The backend change is that a push for a repository no connected source-control
organization covers now CREATES the repository instead of being refused with
repo_not_in_inventory. Both the CLI help and the SDK docstring told customers the
opposite ("It must already be in the org's collected inventory"), which is exactly
the sentence somebody reads before deciding the feature is not for them.
One real addition: `--default-branch` / `default_branch=`. The shipping branch is
the one repository fact a push can contribute that a scan result cannot, and for a
repository LimaCharlie does not collect nothing else can state it at all. Omitted
rather than guessed when the caller does not know it — a default of "main" would
be inventing inventory.
Public repo: draft, for review. Not to be merged by the session.
lcbill
approved these changes
Aug 27, 2026
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
2 participants
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
Documentation only. The wire contract of
POST /cloudsec/{oid}/code/ingestis unchanged, solimacharlie cloudsec code ingestandCloudSec.ingest_code_resultsneeded no code change.What did change is the backend: a push for a repository no connected source-control organization covers now CREATES the repository instead of being refused with
repo_not_in_inventory. Both the CLI help and the SDK docstring told customers the opposite ("It must already be in the org's collected inventory"), which is now false and is exactly the sentence somebody would read before deciding the feature is not for them.The replacement says what the backend actually does: the policy is still the switch, the repository is created carrying only what the push vouches for,
cloudsec code reposshows it withsource: ingest(andbothonce a connection collects it too), it counts against the free tier's repository quota like a collected one, and it is removed with its findings after a month with no push that moves its commit.Public repo — draft, for review. Not to be merged by the session.