Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate click and typer #2110

Closed
5 tasks done
gctucker opened this issue Sep 20, 2023 · 0 comments
Closed
5 tasks done

Investigate click and typer #2110

gctucker opened this issue Sep 20, 2023 · 0 comments
Assignees

Comments

@gctucker
Copy link
Contributor

gctucker commented Sep 20, 2023

The current kci command line tool is based on the same code as in the legacy tools kci_build, kci_test etc. As part of needing a redesign, it's worth considering alternative packages such as click and typer (which is based on click).

Investigating whether we can use them and comparing them can be done by implementing the basic support for loading settings values from TOML for the current command, looking up TOML settings groups based on a config name (e.g. to find an API token for a particular API instance config), implementing some dummy nested commands as well as a real whoami command as a proof-of-concept.

@gctucker gctucker self-assigned this Sep 20, 2023
@gctucker gctucker transferred this issue from kernelci/kernelci-pipeline Sep 20, 2023
@github-project-automation github-project-automation bot moved this from In Progress to Done in KernelCI API & Pipeline Dec 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
1 participant