Repository navigation
Improve confidential request accounting and refresh runtime dependencies - #17
Merged
Merged
Conversation
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.
Updates confidential request accounting, runtime dependencies, and operator configuration conventions.
_API_KEYenvironment names.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
EIF packaging used local test configuration. Nitro hardware execution and production deployment were not performed. Release artifacts must be rebuilt through the existing workflow.