Plug in workflow restrictions to TEEs#22965
Conversation
…ending to the DON. The DON will still enforce if the TEE doesn't
|
👋 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! |
CORA - Pending ReviewersAll codeowners have approved! ✅ Legend: ✅ Approved | ❌ Changes Requested | 💬 Commented | 🚫 Dismissed | ⏳ Pending | ❓ Unknown For more details, see the full review summary. |
|
I see you updated files related to
|
|
✅ No conflicts with other open PRs targeting |
|
e1fb1ec to
254cebf
Compare
| OrgId: contexts.CREValue(ctx).Org, | ||
| Requirements: requirements, | ||
| BinaryUrl: m.binaryURL, | ||
| Restrictions: restrictions, |
There was a problem hiding this comment.
where are these actually checked? In a different PR?
There was a problem hiding this comment.
Yeah, this is a proto in chainlink-protos. We pull in the generated code from chainlink-common.
This PR, you may need to expand the file.
There was a problem hiding this comment.
Right, but where does the relay check the restrictions against the secrets requested? Has that already been merged?
|




No description provided.