Bug 13659 - PRServ should have a read-only port or endpoint
Summary: PRServ should have a read-only port or endpoint
Status: RESOLVED FIXED
Alias: None
Product: BitBake
Classification: Build System, Metadata & Runtime
Component: bitbake (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 4.99
Assignee: Armin Kuster
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2019-11-26 17:04 UTC by Jan-Simon Moeller
Modified: 2021-11-18 16:31 UTC (History)
5 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jan-Simon Moeller 2019-11-26 17:04:31 UTC 
PRServ is currently setup to be read-writable all the time.

If you expose e.g. release artifacts, you will want to expose a PRServ in read-only mode to your users. 

This could just be a end <IP>:<PORT> the daemon binds to but w/o actually accepting new data.
Comment 1 Mark Hatle 2019-12-05 16:25:46 UTC 
Current short term workaround is to distribute the PRServ data to your customers from a read-only location.  (Doesn't really solve the read/write problem..). But keeps them from using your own resources accidentally.

Eventually I would like to create a combined PR Service, hash equivalence, sstate server that would manage the components together and permit features like read-only, etc.

(This more complex would likely be external of the current bitbake mechanism, as it's potentially a lot more complex!)