Dynamically updating action parameters on ST2 UI
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6.5k
- Forks
- 787
- PR merge metrics
- No merged PRs in 30d
Description
In some cases, while calling workflows/actions from the UI, the action parameters (type) might be depend upon another previous action parameter input. For simpler configuration and user experience, and if feasible, it would be good to have capability to accommodate dynamic updating action parameter options based on input values of other parameters.
Example use case:
vSLX chassis type: F4/F8; if F4 is selected, UI should ask for input value for line card slot 1-4 (4 separate inputs), and of F8 is selected, UI should ask input values for line card slot 1-8 (i.e. 8 separate inputs).
Currently (and as shown above), all the input for action params is not dynamic and all 8 line card slot options are given to the user.
Feel free to provide your thoughts, suggestions on this proposal.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points, so first map the ST2 UI action-parameter form and its existing parameter handling. Define how one input should update the available options for another, using the vSLX chassis example as the acceptance case. Done means the UI shows the appropriate number of line-card inputs after selecting F4 or F8.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100