Update TEE constraints to use cre.AnyTee{} and the TS equivalent - #82
Merged
Conversation
product-security-plaid-production
Bot
requested a review
from anirudhwarrier
September 3, 2026 17:43
Darbease
force-pushed
the
update-tee-constraints
branch
from
September 3, 2026 17:45
7c1e47e to
c28135b
Compare
…capability across all confidential workflows
Darbease
force-pushed
the
update-tee-constraints
branch
from
September 3, 2026 17:58
c28135b to
2b7fa12
Compare
thodges-gh
approved these changes
Sep 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
2 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.
update to the Confidential workflows to allow for any enclave and any tee. Currently only supported for us-west-2, but as we add more capability these templates will be able to choose out of what is available. Asked for from Chris Cushman