Bug 13659

Summary: PRServ should have a read-only port or endpoint
Product: [Build System, Metadata & Runtime] BitBake Reporter: Jan-Simon Moeller <dl9pf>
Component: bitbakeAssignee: Armin Kuster <akuster>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Medium+ CC: akuster808, mark.hatle, poky.bs.watcher, poky.watcher, randy.macleod
Version: unspecified   
Target Milestone: 4.99   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Don't know

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!)