stella-ops.org/git.stella-ops.org
1
0
Fork 0
Code Issues Pull Requests Actions 16 Releases Wiki Activity
Files
7b01c7d6acd233c1fdfac71cad09fd266be6bfc9
git.stella-ops.org/docs/implplan/archived/updates/2025-11-01-orch-admin-scope.md
master 7b01c7d6ac
Some checks failed
Docs CI / lint-and-preview (push) Has been cancelled
Details
feat: Add comprehensive product advisories for improved scanner functionality 
- Introduced a blueprint for explainable quiet alerts, detailing phases for SBOM, VEX readiness, and attestations.
- Developed a roadmap for deterministic diff-aware rescans, enhancing scanner speed and efficiency.
- Implemented a hash-based SBOM layer cache to optimize container scans by reusing previous results.
- Created a multi-runtime reachability corpus to validate function-level reachability across various programming languages.
- Proposed a stable SBOM model using SPDX 3.0.1 for persistence and CycloneDX 1.6 for interchange.
- Established a validation plan for quiet scans, focusing on provenance and CI integration.
- Documented guidelines for the Findings Ledger module, outlining roles, execution rules, and testing protocols.
2025-11-17 00:09:26 +02:00

1.7 KiB
Raw Blame History

2025-11-01 · Authority adds Orch.Admin quota controls

What changed

  • Introduced new orch:quota scope and expanded Orch.Admin role for Orchestrator quota, burst, and historical backfill adjustments.
  • Client credential requests for orch:quota now require quota_reason (≤256 chars) and accept optional quota_ticket (≤128 chars). Authority records both values under quota.reason / quota.ticket audit properties.
  • Added dedicated orch:backfill scope. Tokens must include backfill_reason (≤256 chars) and backfill_ticket (≤128 chars); Authority persists them as backfill.reason / backfill.ticket claims and audit properties alongside operator metadata.
  • Tokens embedding orch:quota or orch:backfill expose the corresponding reason/ticket claims so downstream services and audit tooling can trace quota increases or emergency backfills.
  • Console, CLI, and configuration samples include the updated role plus environment variables (STELLAOPS_ORCH_QUOTA_REASON, STELLAOPS_ORCH_QUOTA_TICKET, STELLAOPS_ORCH_BACKFILL_REASON, STELLAOPS_ORCH_BACKFILL_TICKET) for automation.

Why

Quotas and replay backfills materially affect tenant isolation and platform capacity. Capturing explicit operator intent keeps change windows reviewable and aligns with platform audit requirements.

Actions

  1. Update Authority configuration/offline bundles to seed Orch.Admin role for the handful of ops identities that manage quotas.
  2. Adjust automation to pass quota_reason/quota_ticket when exchanging tokens for orch:quota and backfill_reason/backfill_ticket for orch:backfill.
  3. Monitor authority.client_credentials.grant records for the new quota.* and backfill.* audit properties when reviewing change windows.