13659 2019-11-26 17:04:31 +0000 PRServ should have a read-only port or endpoint 2021-11-18 16:31:04 +0000 1 1 7 Build System, Metadata & Runtime BitBake bitbake unspecified x86 Multiple RESOLVED FIXED Medium+ normal 4.99 1 dl9pf akuster akuster808 mark.hatle poky.bs.watcher poky.watcher randy.macleod --- --- Don't know oldest_to_newest 85637 0 dl9pf 2019-11-26 17:04:31 +0000 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. 85734 1 mark.hatle 2019-12-05 16:25:46 +0000 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!) 92042 2 akuster808 2021-11-18 16:31:04 +0000 In the last release. https://git.openembedded.org/bitbake/commit/?h=1.52&id=44287430b9804fcbf2440f85a2424792140e4dc9