feat: display secrets in pipeline run view

[maxy-shpfy]

Description

Added support for displaying secret arguments in task argument values. When a task argument is a secret, it will now be displayed as "🔒 [secret name]" instead of being undefined.

Type of Change

• New feature
• Improvement

Checklist

• I have tested this does not break current pipelines / runs functionality
• I have tested the changes on staging

Test Instructions

Screen Recording 2026-02-17 at 5.29.30 PM.mov (uploaded via Graphite)

1. Create a task with a secret argument
2. Verify that the secret is displayed with a lock icon and the secret name

[maxy-shpfy]

• chore: update vertexAiCompiler #1773
• feat: display secrets in pipeline run view #1772 👈 (View in Graphite)
• feat: use API as secrets storage #1771
• chore: regenerate api based on secrets api backend #1770
• feat: use secrets in submit with arguments dialog #1767
• feat: use secrets in canvas tasks and arguments editor #1766
• feat: secrets management ui #1765
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.

[camielvs]

Is it worth updating the input list as well in the task panel?

Instead of blank it could be the lock + secret name

[camielvs]

Is there any feasible way to give the user feedback if a component is failing due to an invalid secret input?

[camielvs]

^ would be nice to include the above items but can also probably be a follow-up

[maxy-shpfy]

>Is it worth updating the input list as well in the task panel?

It might be tricky - server does not return it in Artifacts response. So we need to dance to match arguments against the inputs which may lead to complications in IOInputs / IOCell etc components. I would investigate that as a separate PR since the change can grow big

[maxy-shpfy]

>Is there any feasible way to give the user feedback if a component is failing due to an invalid secret input?

It will be displayed as a System Error: Error resolving a secret argument for input_name='API_KEY': User developer@localhost does not have secret API_KEY.. Unless server returns some special code, I'm not sure how to determine that for UX-friendly representation that in generic and feasible way.

We can include validation step to match used secrets against available secrets - that's something to consider, but may not be available in every use-case.

[maxy-shpfy]

Merge activity

• Feb 19, 5:34 AM UTC: A user started a stack merge that includes this pull request via Graphite.
• Feb 19, 5:34 AM UTC: @maxy-shpfy merged this pull request with Graphite.