Repository navigation
fix!: harden Security Hub ingestion boundaries - #24
Open
sodle-splunk wants to merge 10 commits into
Open
sodle-splunk wants to merge 10 commits into
sodle-splunk wants to merge 10 commits into
Conversation
Persist a fixed first-run boundary, migrate legacy checkpoints through a conservative UTC lookback, and keep scheduled checkpointing independent of poll-now classification. Authored by Codex.
Request only the remaining local allowance and reject oversized provider pages before accumulating findings. Authored by Codex.
Persist successful finding IDs per SQS message so capped polls resume at the unprocessed tail and delete only after full durable ingestion. Authored by Codex.
|
Merging this PR will release 3.0.0 (2026-08-01)Connector release changes
|
Authored by Codex.
Limit omitted-result pagination to 1,000 findings and exact-ID validation to one page. BREAKING CHANGE: Omitted or oversized finding limits now return at most 1,000 findings per action. Authored by Codex.
Describe the exact retained-item guarantees without implying a single provider request. Authored by Codex.
Scope SQS ingestion progress to a message body and occurrence index so repeated finding identifiers cannot credit unrelated records. Authored-by: Codex
Keep legacy checkpoints conservative, rotate capped message retries, continue later direct findings, and report deferred or invalid queue records. Authored-by: Codex
Persist deferred message order so a repeatedly failing record cannot monopolize the poll cap and starve later received messages. Authored-by: Codex
Avoid a second unbounded related-findings request after exact-ID validation by reusing the already validated bounded response. Authored-by: Codex
Contributor
Author
|
Codex scope update: connector-local hardening is complete and core gates are green. Invocation-mode classification and pre-materialization response caps are platform follow-ups and do not block this PR. Marking it ready for review. |
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.
Written and implemented by Codex.
Summary
These are separate commits with matching release-note entries so their release history remains independently reviewable.
Tracking
Verification
dee5a7b115775e83d73b03958aba6bfc8c2a7417dee5a7b115775e83d73b03958aba6bfc8c2a7417dee5a7b115775e83d73b03958aba6bfc8c2a7417dee5a7b115775e83d73b03958aba6bfc8c2a7417Integration and shared sanity testing are outside this workflow and do not block review.
Connector scope and residual platform work
Connector-local hardening in this PR is complete and core checks are green.
BaseConnectorowns that behavior.Those platform residuals do not block review or merge of the completed connector improvements.
Release impact
This intentionally produces a major release: omitted or oversized finding limits now return at most 1,000 findings per action, and exact-ID validation retains at most 100 findings. Scheduled polling may also conservatively revisit its configured lookback once while migrating legacy checkpoint state; stable source identifiers keep that overlap idempotent.
Merge strategy: merge commit only; do not squash.