Skip to content
Snippets Groups Projects

OBS ACL Feature documentation

Closed Ritesh Raj Sarraf requested to merge wip/ritesh/obs-acl-feature into master
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

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
  • Martyn Welch
  • Martyn Welch
    Martyn Welch @martyn started a thread on commit e2750eb7
  • 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)
    • Don't provide links to tasks - very few people have access to those. Explain the context here to avoid the need to go look elsewhere.

    • Author Maintainer

      Yes. I mean that was my thought to just have a link. So that, people who need more information, should be able to access it through the task. Others, who shouldn't have a detailed view, will not be allowed by Phabricator.

    • Please register or sign in to reply
  • Martyn Welch
  • Martyn Welch
    Martyn Welch @martyn started a thread on commit e2750eb7
  • 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.
    • If we're going to mention specific product teams (especially when we are using acronyms), I really think this needs to be in the private designs. Which is also generated using Hugo, so moving it is trivial...

    • Author Maintainer

      I thought of this and felt PT was generic enough as a Product Team There were references to Guradian Project, which I removed to ensure no names are provided. But, it looks like, PT is a name in itself within Bosch.

      But I only interpreted it as an acronym for Product Team

    • Please register or sign in to reply
  • Martyn Welch
    Martyn Welch @martyn started a thread on commit e2750eb7
  • 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" >}}
    • I'm quite interested to see how these get formatted. The pure Markdown way would be:

      ![App repository Private](/images/app_repo_hidden_meta_conf.png)

      Though that's not rendering the alt text at the moment and doesn't actually add a title to the image that this would appear to do.

    • Please register or sign in to reply
  • added 1 commit

    • d9aa87d9 - Apply 1 suggestion(s) to 1 file(s)

    Compare with previous version

  • added 1 commit

    • a2c2179b - Drop title and icrease heading font by 1 pt

    Compare with previous version

  • added 4 commits

    • 3af6ceb1 - 1 commit from branch master
    • 18bf4b6e - Document the OBS ACL feature
    • 5c8675ab - Apply 1 suggestion(s) to 1 file(s)
    • 5d2d6295 - Drop title and icrease heading font by 1 pt

    Compare with previous version

  • Please register or sign in to reply
    Loading