Discrepancy between 'st2 action get core.http' and GUI metadata display
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6.5k
- Forks
- 787
- PR merge metrics
- No merged PRs in 30d
Description
At user level, on st2 2.2.1, in order to retrieve the fields from st2 required to run the core.http action, you have to return both the metadata from the action and the http-request runner. If you however open the GUI up and inspect the action and it's input fields, they are different and appear to be a combination of both runner and action.
Is this a bug with the CLI Client not taking the fields from the runner and adding them to the those of the action?
I don't have a solution nor have I looked in to why. From a user experience, it's inconsistent and for new comers that experience this during training, it's entirely frustrating.
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 reproducing the discrepancy in st2 2.2.1 with st2 action get core.http, then inspect the same action and its input fields in the GUI. Compare the metadata returned for the action with the metadata from the http-request runner. Done means the CLI and GUI present consistent input fields, or the difference is clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100