Shell Command Inputs - Lookup Type linked to Lookup Attributes on the Shell #1481
Quali-Community
started this conversation in
Idea Box
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Now that the API supports the ability to update lookup values for attributes, and this is being used for Discovery/App building, I would like to be able to have/extend similar functionality to a Command Input.
This would allow for a Command's input to be dynamic updated - possible based on updates that occur. Example may be to inquire about specific services/configuration options enabled or deployed to that device. Or to Enable or Disable similar - you would update the "Enable" & "Disable" list as you turn on or off a service/feature for a device.
This would require a custom attribute be added to handle this data for the command, but that information has to be stored somewhere, and we have
In the Drivermetadata.xml, I would like to be able to list the Type as "Attribute" and maybe the "AllowedValue" as the FamilyName.AttributeName
Example:
<Command DisplayName="Get NSO Services Info" Name="request_NSO_service_detail" Description="Get details about an NSO service deployed to this device"> <Parameters> <Parameter DisplayName="Service Name" Type="Attribute" Mandatory="False" Name="command_name" AllowedValue="FamilyName.AttributeName" Description="Select a service deployed to this resource"/> </Parameters> </Command>There are probably more possibilities that I'm not thinking of, but just allowing the drivermetadata.xml to display a lookup attribute gives us some possibilities.
TSI Support (techsupport@tsieda.com) - 11/23/2022 06:55 PM
· 5692 ·
Beta Was this translation helpful? Give feedback.
All reactions