feat: use secrets in canvas tasks and arguments editor#1766
Merged
maxy-shpfy merged 1 commit intomasterfrom Feb 19, 2026
Merged
Conversation
Collaborator
Author
This was referenced Feb 6, 2026
f8de3f0 to
ff72e68
Compare
This was referenced Feb 9, 2026
ff72e68 to
76e1ba3
Compare
303639b to
d6d2dda
Compare
76e1ba3 to
ffe4c37
Compare
d6d2dda to
cf6fc56
Compare
ffe4c37 to
8de520a
Compare
cf6fc56 to
e8338b5
Compare
8de520a to
a166e29
Compare
e8338b5 to
ca5ca10
Compare
a166e29 to
211cc35
Compare
ca5ca10 to
9de690a
Compare
211cc35 to
fd03b48
Compare
Mbeaulne
reviewed
Feb 18, 2026
fd03b48 to
b89e896
Compare
9de690a to
0bf5e60
Compare
Mbeaulne
reviewed
Feb 18, 2026
Mbeaulne
reviewed
Feb 18, 2026
b89e896 to
27f3a22
Compare
0bf5e60 to
dca099d
Compare
27f3a22 to
cd0cdde
Compare
camielvs
reviewed
Feb 18, 2026
| <Icon | ||
| name="Lock" | ||
| size="xs" | ||
| className="text-amber-600 shrink-0" |
Collaborator
There was a problem hiding this comment.
Makes me wonder if we should set a tailwind css class for text-secret, bg-secret etc
camielvs
approved these changes
Feb 18, 2026
Collaborator
camielvs
left a comment
There was a problem hiding this comment.
Small nits but otherwise LGTM
Collaborator
|
Actually, one question which is probably applicable later in the stack but I'm going to ask it here: if I set a task argument to be a secret then clone the pipeline, what happens? Similarly, if I run the pipeline and someone clones, what happens to the secret? |
dca099d to
a448d6e
Compare
0ea1669 to
dd2207d
Compare
3e47629 to
a348073
Compare
dd2207d to
a213ecb
Compare
a348073 to
e1c5d1f
Compare
a213ecb to
6918412
Compare
6918412 to
963e0c9
Compare
Collaborator
Author
|
^ cloning secrets into "inputs" is not possible due to Spec Schema limitations of inputs. Secret used as arguments in tasks- will stay as is. Run will fail if no same secret available in user's vault |
Collaborator
Author
Merge activity
|
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
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.

Description
Added support for secret arguments in the task node UI. Users can now select secrets from a dialog and use them as argument values. Secret arguments are displayed with a lock icon and special formatting to distinguish them from regular values.
Type of Change
Checklist
Screenshots (if applicable)
Secret in Arguments and Canvas.mov (uploaded via Graphite)
Test Instructions
Additional Comments
This implementation includes: