Support Dynamic Enums in the Actions UI
Open
Nobody has claimed this yet.
feature
proposal
- Dominant language
- Python
- Stars
- 6.5k
- Forks
- 787
- PR merge metrics
- No merged PRs in 30d
Description
Rundeck allows for an input type using a dynamically generated enum, e.g. list of kubernetes clusters. It would be nice to see an equivalent in ST2
- Ability in action specs to specify a source of enum data, e.g. a REST call or python call
- Server side API to bridge UI to information source (with RBAC) - all lookups should happen serverside
- Triggers on other input fields to regenerate enums based on a field change (e.g. workloads in a k8s cluster after cluster is selected)
- Initial state/fallback/"all" options
- Support single item list and list of tuples with ( display, value )
- Pagination/search for large lists (Rundeck supports >10K nodes for example)
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
Start by mapping the action-spec entry points, Actions UI, and server-side API/RBAC boundaries named in the issue. Define how dynamic sources, dependent-field refreshes, fallback options, tuple values, and pagination/search should work, then identify the relevant tests; done means the complete behavior is specified and covered across UI and server components.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, authorization, backend, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100