Process config attributes / options in the order defined in the config schema when using "pack config" CLI command
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6.5k
- Forks
- 787
- PR merge metrics
- No merged PRs in 30d
Description
Right now attributes are not processed / displayed in the order defined in the config schema when using st2 pack config command. This could be a bit confusing to the user.
This ties into the age old "preserve ordering when reading and writing out YAML files" issue.
This is not a big blocker for now, but something we should fix in the future to provide a better user experience.
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 at the st2 pack config CLI command and trace how the config schema and YAML data are read before attributes are processed or displayed. The work is done when attributes consistently follow the order defined in the config schema while preserving the relevant YAML ordering behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100