Skip to content

Refresh internal KMS trust and deliver durable monitor alerts - #5

Merged
leonacostaok merged 1 commit into
mainfrom
feat/consumer-runtime
Oct 13, 2026
Merged

leonacostaok merged 1 commit into
mainfrom
feat/consumer-runtime

Conversation

@leonacostaok

Copy link
Copy Markdown
Member

The persistent consumer needs current internal key status and a reliable path from queued findings to delivered alerts. Add a bounded KMS refresher that checks the configured key and public-key pin, plus consumer enforcement of receipt freshness, rollback protection and an independent local withdrawal override.

Add Resend delivery using the existing runtime credential and an explicitly configured recipient. Durable sending intents, provider receipts and occurrence-specific acknowledgments preserve pending alerts through timeouts and restarts. Delivery polling distinguishes provider acceptance from delivery, rotates failed batches fairly and stops ambiguous resubmission before the provider's idempotency window expires.

@leonacostaok
leonacostaok merged commit 3a459dd into main Oct 13, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant