OBS ACL Feature documentation
3 unresolved threads
3 unresolved threads
This MR aims to document the OBS ACL feature implemented in-house. For more details, please see task AT5645. https://phabricator.apertis.org/T5645
Signed-off-by: Ritesh Raj Sarraf ritesh.sarraf@collabora.com
Merge request reports
Activity
requested review from @martyn
- Resolved by Ritesh Raj Sarraf
- Resolved by Ritesh Raj Sarraf
- content/guides/obs-acl-feature.md 0 → 100644
1 --- 2 subtitle: "OBS Access Control List Feature" 3 tags: [OBS, ACL] 4 --- 5 6 # OBS ACL Feature 7 8 This document outlines the OBS ACL feature that has been implemented on the Collabora instance of OBS. For a detailed background on the implementation, please see task [AT5645](https://phabricator.apertis.org/T5645) - Resolved by Ritesh Raj Sarraf
- content/guides/obs-acl-feature.md 0 → 100644
1 --- 2 subtitle: "OBS Access Control List Feature" 3 tags: [OBS, ACL] 4 --- 5 6 # OBS ACL Feature 7 8 This document outlines the OBS ACL feature that has been implemented on the Collabora instance of OBS. For a detailed background on the implementation, please see task [AT5645](https://phabricator.apertis.org/T5645) 9 10 11 ## Background 12 As an Apertis maintainer, i need to support creation of different projects in OBS for multiple product teams and restricting the access to only for developers of the product. 13 14 ## Usecase 15 For a product team PT, we need to hide all PT related projects (pt:target, pt:development. pt:sdk) from other teams, with only PT team should be allowed to see and use this projects. - content/guides/obs-acl-feature.md 0 → 100644
56 57 Next, we have `app-repo-public`, which is a public repository, and thus will not have access to the `base-repo-hidden` repository. 58 59 And finally, we have `app-repo-allow-build-dep`, which is also a public repository, and thus will not have access to the `base-repo-hidden` repository. The `app-repo-allow-build-dep` repository is marked as an exception through the `<allowbuilddep ....>` attribute in the meta configuration for `base-repo-hidden` repository, thus granting it access to the `base-repo-hidden` repository. 60 61 62 ### home:ritesh:apertis:demo:base-repo-hidden 63 This is the base OBS repository. This repository houses our private package (in this example, `debhelper`) which will be used by packages in other repositories as their build dependency 64 65 {{< figure src="/images/base_repo_meta_conf.png" alt="Base repository Private" title="Base repository Private" >}} 66 {{< figure src="/images/base_repo_overview.png" alt="Base repository Private overview" title="Base repository Private overview" >}} 67 68 ### home:ritesh:apertis:demo:app-repo-hidden 69 This is an example OBS repository which houses an application. This repository is also set as a private repository. Thus this repository will have access to packages from the base repository, which in this case would mean: `usrmerge => debhelper`. This is because a private repository can access the contents of another private repository. 70 71 {{< figure src="/images/app_repo_hidden_meta_conf.png" alt="App repository Private" title="App repository Private" >}} Closing this MR as the review has moved to https://gitlab.apertis.org/docs/apertis-designs-private/-/merge_requests/74
Please register or sign in to reply