Compose fixes, anonymous worker auth, additional API filters #199
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I am adapting my Web UI to the v1 API and found a few issues along the way.
Opening this as a draft just to get some feedback. Since I am changing rebuilderd and UI side by side I'll keep this in a single branch for now but I can open separate MRs for final as/if any of the points below are ACKed. Also, I haven't written a single line of rust in my life until now so I am learning as I go and there is "vibe" coding involved.. please have patience.
README.mdandrebuilderd.confcomments, out of the box there should be no authentication and workers should be able to register anonymously. However, v1 auth code requires a key regardless. This breaks default compose (workers getting 403). I added a sample code which ignores auth and just registers a worker if config is not set but it could also go with a different approach to use some "changeme" key by default. This one is mostly for @Nihlusdistributions/archlinux/???/components/core/architecturesso I added a null handler but that is ugly. I guess the proper answer to this issue is to simply use/distributions/archlinux/architecturesbut I need to handle this case by case in the UI. Would it make sense to userollingkeyword for arch release instead of NULL? That would nicely solve the problem but maybe it's not a good idea for some reason.