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 54
    • Issues 54
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 12
    • Merge requests 12
  • 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
  • !218

Update legal tag compliance

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Akansha Rajput[Microsoft] requested to merge UpdateLegalTagCompliance into master Jun 22, 2021
  • Overview 83
  • Commits 18
  • Pipelines 32
  • Changes 29

Type of change

  • [ Feature ]

Please provide link to gitlab issue or ADR(Architecture Decision Record)
When a legal tag change happens or if it expires, we need to accordingly update the records with the invalid legal tags and accordingly notify further in the system to have them not visible for search and other use cases.

This MR changes contain storage side wiring for the events from legal service on tag expiration.

Does this introduce a change in the core logic?

  • [NO]

Does this introduce a change in the cloud provider implementation, if so which cloud?

  • Azure

Does this introduce a breaking change?

  • [NO]

What is the current behavior?

Storage service Azure has no subscriber logic to it, this MR focuses on adding that logic and using that to subscribe legal tag changed event. It further process that event and updates the compliance on invalidated records.

What is the new/expected behavior?

Storage service will subscribe to legal tag change event and update compliance accordingly.

Have you added/updated Unit Tests and Integration Tests?

Yes - Added relevant unit tests.

Any other useful information

Please find flow and design details here https://dev.azure.com/ms-slb-cobuild/ms-slb-delfi-collab/_workitems/edit/259

Edited Jun 23, 2021 by Hema Vishnu Pola [Microsoft]
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: UpdateLegalTagCompliance