You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm currently able to define a global output parameter in my spec, which I can either access using argo get my-workflow, programmatically, or looking at the yaml definition in the UI. I'd like to extent the Output Artefacts tab to also include any output parameters, for convenient visibility in the UI.
Motivation
For explainability reasons, I would like to output a few global parameters once a workflow is completed. Ideally users of the platform in our company could more easily access this information by simply going to the Outputs (currently Output Artefacts) tab, instead of sifting through yaml to find them.
Proposal
Split the Output tab into two sections: Artefacts and Global Parameters, and list out the parameters there.
Message from the maintainers:
If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.
The text was updated successfully, but these errors were encountered:
Summary
I'm currently able to define a global output parameter in my spec, which I can either access using
argo get my-workflow
, programmatically, or looking at the yaml definition in the UI. I'd like to extent theOutput Artefacts
tab to also include any output parameters, for convenient visibility in the UI.Motivation
For explainability reasons, I would like to output a few global parameters once a workflow is completed. Ideally users of the platform in our company could more easily access this information by simply going to the
Outputs
(currentlyOutput Artefacts
) tab, instead of sifting through yaml to find them.Proposal
Split the
Output
tab into two sections: Artefacts and Global Parameters, and list out the parameters there.Message from the maintainers:
If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.
The text was updated successfully, but these errors were encountered: