Skip to content

Improve confidential request accounting and refresh runtime dependencies - #17

Merged
hcastc00 merged 1 commit into
mainfrom
maintenance/runtime-request-accounting
Oct 26, 2026
Merged

hcastc00 merged 1 commit into
mainfrom
maintenance/runtime-request-accounting

Conversation

@hcastc00

@hcastc00 hcastc00 commented Oct 26, 2026 •

Copy link
Copy Markdown
Contributor

Updates confidential request accounting, runtime dependencies, and operator configuration conventions.

  • Scope request tracking and quotas by account, shared across API keys.
  • Use FIFO expiration while preserving duplicate-request handling and encrypted error responses.
  • Standardize provider credential references on uppercase _API_KEY environment names.
  • Normalize request IDs, simplify bearer-token CORS, and align Nitro metrics binding with its network profile.
  • Update Go to 1.26.10, refresh dependencies and the pinned enclave builder, and add dependency checks for ordinary and Nitro builds.
  • Document request limits, credential naming, and PII masking coverage.

Compatibility

Confidential requests have an account allowance of 10,000 retained request IDs over three minutes. Exceeding it returns 429 with confidential_request_limit_exceeded.

Custom provider credential aliases must use uppercase names ending in _API_KEY. Unsupported request IDs are replaced with generated UUIDs.

Validation

  • Full Go suite passed on the host and in a Linux container.
  • Focused race checks and dependency checks passed.
  • Linux Nitro networking, bootstrap, and build-profile tests passed.
  • Nitro binaries and test packages cross-compiled for Linux amd64 and arm64.
  • Ordinary gateway and amd64 enclave Docker images built successfully.
  • Packaged gateway startup, health, request-ID, bearer CORS, and metrics checks passed.
  • Two clean enclave image builds produced identical image IDs. Two EIF files passed CRC checks and had matching PCR0/PCR1/PCR2 measurements.

EIF packaging used local test configuration. Nitro hardware execution and production deployment were not performed. Release artifacts must be rebuilt through the existing workflow.

@hcastc00
hcastc00 merged commit 22966e3 into main Oct 26, 2026
5 checks 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