Uploaded image for project: 'OpenShift Pipelines'
  1. OpenShift Pipelines
  2. SRVKP-3542

No fallback on OWNERS from PaaC Policy

XMLWordPrintable

    • 3
    • False
    • Hide

      None

      Show
      None
    • False
    • When policy is set and it did not match we were not falling back to other ACL rules and we were not checking if the other ACL rules were matching (like if the user would have explicit access to OWNERS file).
    • Pipelines Sprint 247, Pipelines Sprint 249

      Description of problem:

      Fallback on the OWNERS file should work when PaaC Policy is used

      Prerequisites (if any, like setup, operators/versions):

      Steps to Reproduce

      • create a user with no collabo right onto target repo or org
      • create a policy on repo CR  giving access to a group of users but not the one we have just created.
      • create a OWNER files with the created user in it
      • ensure it works by creating a  PR as new user from a fork to the target repo.

       

      Actual results:

      Expected results:

      Reproducibility (Always/Intermittent/Only Once):

      Acceptance criteria: 

       

      Definition of Done:

      Build Details:

      Additional info (Such as Logs, Screenshots, etc):

       

       *

              cboudjna@redhat.com Chmouel Boudjnah
              cboudjna@redhat.com Chmouel Boudjnah
              Piyush Garg Piyush Garg
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: