Merge TEE code to main - #437
Conversation
|
|
👋 nolag, 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! |
|
The latest Buf updates on your PR. Results from workflow Regenerate Protobuf Files / buf (pull_request).
|
|
|
||
| message CapabilityRestrictions { | ||
| repeated CapabilityRestriction restrictions = 1; | ||
| int32 max_total_calls = 2; |
There was a problem hiding this comment.
Matches capabilites dev: https://github.com/smartcontractkit/chainlink-protos/blob/capabilities-development/cre/sdk/v1alpha/sdk.proto#L213
You only changed secrets in #436. I can change this one too, but it would break TEEs using it. Idk there status. That said, the break shouldn't matter since -ve numbers were'nt used.
There was a problem hiding this comment.
@russell-stern , what do you want me to do?
Needed for the enclave to forward org identity when fetching secrets from VaultDON via the confidential relay path. (cherry picked from commit 5b99921)
…ies-development Field 9 is reserved for sdk_execute_request (added on capabilities-development by a commit not cherry-picked here); restrictions must stay at 10 to match capabilities-development's wire numbering.
3 participants
See commits from capabilities dev, already been approved there