Skip to content
GitLab
  • Menu
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 56
    • Issues 56
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 13
    • Merge requests 13
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & 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 Software
  • Platform
  • System
  • Storage
  • Merge requests
  • !154

process only the right set of metadata during bulk update records

  • Review changes

  • Download
  • Email patches
  • Plain diff
Closed Alok Joshi requested to merge metadata_update_fix into master Mar 03, 2021
  • Overview 0
  • Commits 4
  • Pipelines 11
  • Changes 2

During bulk update, even records to which user is unauthorized to have access to were getting processed, resulting in downstream issues when calling cloud functions. To void this, we need to remove those records from being processed from the bulk update method.

This is a fix to address an internal bug raised

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: metadata_update_fix