Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • S Storage
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 46
    • Issues 46
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 15
    • Merge requests 15
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Open Subsurface Data Universe SoftwareOpen Subsurface Data Universe Software
  • Platform
  • System
  • Storage
  • Merge requests
  • !37

Enforce that user must have ACL groups access of the Record for purge, create and update operations.

  • Review changes

  • Download
  • Email patches
  • Plain diff
Closed Johnny Guo requested to merge enforce-record-owner-access into master Jul 14, 2020
  • Overview 2
  • Commits 6
  • Pipelines 13
  • Changes 9

• What is the change? This change is to make sure that if a user wants to purge/update/create a record, the user must have access to record ACL groups, which means be a member of any ACL group of the record.

• What does it impact? If a user does not belong to any ACL group of the record, he/she cannot update/create/purge it after the PR is merged.

• How do I reproduce or test the change? Here I add and update unit tests and integration tests, you can also manually test the deployment.

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: enforce-record-owner-access