Open LordTermor opened 3 months ago
Some commands that seem sensible to me:
bxt upload <package>
bxt compare <package1> <package2>
Would this work? What we need else?
We discussed a bit and the commands of https://s3tools.org/s3cmd looks reasonable. But probably not all of its commands are needed and on the other side we need some other commands.
project started at https://github.com/fhdk/bxtctl
[main] $ poetry run bxtctl -h
bxt user: 'default' has access to:
Branches : {'stable', 'unstable', 'testing'}
Architectures : {'aarch64', 'x86_64'}
Repositories : {'core'}
usage: bxtctl [-h] [-b {stable,unstable,testing}] [-r {core}] [-a {aarch64,x86_64}] [-p PACKAGE [PACKAGE ...]] {commit,compare,configure,login,ls,shell}
Command line tool for bxt package management.
positional arguments:
{commit,compare,configure,login,ls,shell}
Command to execute
options:
-h, --help show this help message and exit
-b {stable,unstable,testing}, --branch {stable,unstable,testing}
Target Branch
-r {core}, --repo {core}
Target Repository
-a {aarch64,x86_64}, --archictecre {aarch64,x86_64}
Target Architecture
-p PACKAGE [PACKAGE ...], --package PACKAGE [PACKAGE ...]
Target Package
bxtctl v.0.1.0 - AGPL v3 or later <https://www.gnu.org/licenses/agpl.html>
Headsup for @fhdk: https://github.com/anydistro/bxt/pull/34 is now merged, check out new swagger (I removed deployment endpoints from there, they don't make sense as a part of overall API)
Updated bxtctl to 0.2.0 to work with changed API
While web UI is pretty convenient, we might need to have a CLI version for scripting and other use cases when ui is too excessive