Quick Access Parameters

[mmackay21724]

Feature Request:: (unless it's already there) - Non Critical
In Quick access the parameter provided is labeled based on the variable name.
e.g.

vpn_address
reservation.com:20371    

Would be good to have a label instead.
e.g.

outputs: 
  fmc_server:
    value: '{{ .grains.sbx_creds.outputs.password }}'
    label: 'FMC Server'
    

[TomerAdmon]

Thanks @mmackay21724! 😍

Where would you expect to see the label/alias presented? in what use cases do you feel you need this additional data on the output?

[mmackay21724]

We use this to present information specific to a reservation. e.g. VPN connection, passwords etc.

Although our users are supposed to intelligent and should be able to determine the purpose based on variable name from a UI/UX perspective it would be cleaner to and probably more secure to show a label

[mmackay21724]

[Chris530906]

Hello @mmackay21724 we do have this feature already but its not clearly documented. We support spaces in our Blueprint level Inputs and Outputs as seen below:

Just be aware if you are nesting blueprints and want to pass the outputs of a nested BP to the top level, be sure to encase the output name as shown below:

We will also update our documentation to better explain this feature. Thank you again for bringing this to our attention and for your patience.

[mmackay21724]

Oh cool thanks. I’ll have a play Mike From: Chris530906 ***@***.***> Date: Tuesday, October 3, 2023 at 10:17 AM To: QualiTorque/qualitorque.github.io ***@***.***> Cc: Mike Mackay (mmackay) ***@***.***>, Mention ***@***.***> Subject: Re: [QualiTorque/qualitorque.github.io] Quick Access Parameters (Discussion #335) Hello @mmackay21724<https://github.com/mmackay21724> we do have this feature already but its not clearly documented. We support spaces in out Blueprint level Inputs and Outputs as seen below: [image]<https://user-images.githubusercontent.com/73956778/272344674-37193bf4-59a0-4b8c-a3a8-9db3aa746c37.png> [image]<https://user-images.githubusercontent.com/73956778/272345739-65fc8538-eee8-4571-a9b3-cbd03160d4c9.png> Just be aware if you are nesting blueprints and want to pass the outputs of a nested BP to the top level, be sure to encase the output name as shown below: [image]<https://user-images.githubusercontent.com/73956778/272345468-e3510329-3938-4c58-8eab-ba593e18261e.png> We will also update our documentation to better explain this feature. Thank you again for bringing this to our attention and for your patience. — Reply to this email directly, view it on GitHub<#335 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AD32QFGUTGL2JO5E4HB6AJ3X5RCCFAVCNFSM6AAAAAA5RHX3YWVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TCNZYGMZTK>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[TomerAdmon]

@mmackay21724 @Chris530906 - Thank you for your contribution! 😍😍

We've updated our documentation to include how to use friendly outputs and inputs in the Torque blueprint YAML.
PR - #336
Info added here - https://docs.qtorque.io/blueprint-designer-guide/blueprints/blueprints-yaml-structure#outputs