Skip to content

settings: add Confidential Compute enclave request timeouts (PRIV-504)#2211

Merged
prashantkumar1982 merged 1 commit into
mainfrom
priv-504-cw-limits-d
Jul 1, 2026
Merged

settings: add Confidential Compute enclave request timeouts (PRIV-504)#2211
prashantkumar1982 merged 1 commit into
mainfrom
priv-504-cw-limits-d

Conversation

@prashantkumar1982

@prashantkumar1982 prashantkumar1982 commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

What

Adds two node-level settings to the ConfidentialCompute block of the CRE limits framework:

  • ConfidentialCompute.EnclaveRequestTimeout (Setting[time.Duration], default 30s)
  • ConfidentialCompute.PublicKeyRequestTimeout (Setting[time.Duration], default 5s)

Regenerates the golden defaults.json / defaults.toml (go test . -update) and adds the two keys to the README flowchart so TestFlowchartComplete passes.

@github-actions

github-actions Bot commented Jul 1, 2026

Copy link
Copy Markdown
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!

@github-actions

github-actions Bot commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

✅ API Diff Results - github.com/smartcontractkit/chainlink-common

✅ Compatible Changes (2)

pkg/settings/cresettings.confidentialCompute (2)
  • EnclaveRequestTimeout — ➕ Added

  • PublicKeyRequestTimeout — ➕ Added


📄 View full apidiff report

@prashantkumar1982 prashantkumar1982 added this pull request to the merge queue Jul 1, 2026
Merged via the queue into main with commit 1446a98 Jul 1, 2026
33 checks passed
@prashantkumar1982 prashantkumar1982 deleted the priv-504-cw-limits-d branch July 1, 2026 16:10
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.

3 participants