PRIV-592: Add Confidential Compute limits (TLS, cache, session)#2220
Merged
Conversation
Resolve cresettings conflicts: keep main's EnclaveRequestTimeout and PublicKeyRequestTimeout plus the 1A ConfidentialCompute limits (TLS, refresh interval, public-key cache, session). Co-authored-by: Cursor <cursoragent@cursor.com>
Contributor
|
👋 prashantkumar1982, thanks for creating this pull request! To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team. Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks! |
prashantkumar1982
changed the title
Contributor
✅ API Diff Results -
|
prashantkumar1982
changed the title
vreff
approved these changes
Jul 3, 2026
pavel-raykov
approved these changes
Jul 3, 2026
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
3 participants
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.
Summary
ConfidentialComputecresettings with the remaining capability-side executor settings from PRIV-592: TLS verification skip, enclave refresh interval, public-key cache tuning, and sticky-session config.confidential-compute(enclave-client.DefaultCacheConfig,DefaultSessionConfig, etc.) so behavior is unchanged until explicitly overridden via limits.New settings keys:
ConfidentialCompute.InsecureSkipTLSVerifyfalseConfidentialCompute.EnclaveRefreshInterval10sConfidentialCompute.PublicKeyCache.*DefaultCacheConfigConfidentialCompute.Session.*DefaultSessionConfigCompanion PR in
confidential-computewill consume these settings in the executor while keeping deprecated job-spec fields as transitional overrides.