linux/poky.git/bitbake/bin/bitbake-hashserv, branch scarthgap-5.0.1

bitbake: hashserv: improve the loglevel error message to be more helpful

2024-02-19T11:58:12+00:00

Coming from a kernel background, I was thinking along the lines of dmesg -n for loglevel adjustments. So I tried various large and small and even zero number values with no luck before getting frustrated and opening up the python. Let us save others the frustration and give a hint what the args it expects should look like. (Bitbake rev: df184b2a4e80fca847cfe90644110b74a1af613e) Signed-off-by: Paul Gortmaker Signed-off-by: Richard Purdie

bitbake: bitbake-hashserv: Add description of permissions

2023-12-18T09:18:01+00:00

Adds a text description of the possible permissions in the hash server help text (Bitbake rev: 8295ac1b6672c25bee595cff6e000b2af817f904) Signed-off-by: Joshua Watt Signed-off-by: Richard Purdie

bitbake: bitbake-hashserver: Allow anonymous permissions to be space separated

2023-11-09T17:33:03+00:00

Space separation is more natural when setting the value from an environment variable, so allow that here for convenience. (Bitbake rev: 07eb9176f8a7449c1d2cbfff072fa0873e97a336) Signed-off-by: Joshua Watt Signed-off-by: Richard Purdie

bitbake: hashserv: Add user permissions

2023-11-09T17:33:03+00:00

Adds support for the hashserver to have per-user permissions. User management is done via a new "auth" RPC API where a client can authenticate itself with the server using a randomly generated token. The user can then be given permissions to read, report, manage the database, or manage other users. In addition to explicit user logins, the server supports anonymous users which is what all users start as before they make the "auth" RPC call. Anonymous users can be assigned a set of permissions by the server, making it unnecessary for users to authenticate to use the server. The set of Anonymous permissions defines the default behavior of the server, for example if set to "@read", Anonymous users are unable to report equivalent hashes with authenticating. Similarly, setting the Anonymous permissions to "@none" would require authentication for users to perform any action. User creation and management is entirely manual (although bitbake-hashclient is very useful as a front end). There are many different mechanisms that could be implemented to allow user self-registration (e.g. OAuth, LDAP, etc.), and implementing these is outside the scope of the server. Instead, it is recommended to implement a registration service that validates users against the necessary service, then adds them as a user in the hash equivalence server. (Bitbake rev: 69e5417413ee2414fffaa7dd38057573bac56e35) Signed-off-by: Joshua Watt Signed-off-by: Richard Purdie

bitbake: hashserv: Add SQLalchemy backend

2023-11-09T17:33:02+00:00

Adds an SQLAlchemy backend to the server. While this database backend is slower than the more direct sqlite backend, it easily supports just about any SQL server, which is useful for large scale deployments. (Bitbake rev: e0b73466dd7478c77c82f46879246c1b68b228c0) Signed-off-by: Joshua Watt Signed-off-by: Richard Purdie

bitbake: bitbake-hashserv: Allow arguments from environment

2023-11-09T17:33:02+00:00

Allows the arguments to the bitbake-hashserv command to be specified in environment variables. This is a very common idiom when running services in containers as it allows the arguments to be specified from different sources as desired by the service administrator (Bitbake rev: f65c87fab07a730f2f4588764cb64508c2149b40) Signed-off-by: Joshua Watt Signed-off-by: Richard Purdie

bitbake: bitbake: enable python warnings at the first opportunity

2021-09-19T10:33:14+00:00

We really do want to see those, as they tend to turn into hard errors eventually, as what happened with collections vs collections.abc in python 3.10. (Bitbake rev: bc43fbb86361a21dc2d5deb910810c5a77fdabe8) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

bitbake: hashserv: Add short forms of remaining command line arguments

2021-02-10T23:48:16+00:00

Short form arguments are added for convenience. (Bitbake rev: 921199a4923ce383b27e23c9b7e34eb785c8bae3) Signed-off-by: Paul Barker Signed-off-by: Richard Purdie

bitbake: hashserv: Support upstream command line argument

2021-02-10T23:48:16+00:00

The hashserv server already implements support for pulling hash data from another "upstream" server. Add the -u/--upstream argument to the bitbake-hashserv app to expose this functionality to users. (Bitbake rev: 8de510f1de35e581bcd5858edf23619c6a4cf923) Signed-off-by: Paul Barker Signed-off-by: Richard Purdie

bitbake: hashserv: Support read-only server

2021-02-10T23:48:16+00:00

The -r/--readonly argument is added to the bitbake-hashserv app. If this argument is given then clients may only perform read operations against the server. The read-only mode is implemented by simply not installing handlers for write operations, this keeps the permission model simple and reduces the risk of accidentally allowing write operations. As a sqlite database can be safely opened by multiple processes in parallel, it's possible to start two hashserv instances against a single database if you wish to export both a read-only port and a read-write port. (Bitbake rev: 492bb02eb0e071c792407ac3113f92492da1a9cc) Signed-off-by: Paul Barker Signed-off-by: Richard Purdie