Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • S Storage
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 53
    • Issues 53
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 17
    • Merge requests 17
  • 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
  • !111

Azure implementing metadata patch API

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Jason requested to merge azure-implementing-metadata-patch-api into master Dec 16, 2020
  • Overview 1
  • Commits 4
  • Pipelines 6
  • Changes 2

Type of change

  • Bug Fix
  • Feature

Please provide link to gitlab issue or ADR(Architecture Decision Record)

#10 (closed)

Does this introduce a change in the core logic?

  • [YES/NO]

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

  • AWS
  • Azure
  • GCP
  • IBM

Does this introduce a breaking change?

  • [YES/NO] this introduces a breaking change to current environments running storage in that their integration tests will fail. These new integration tests that have been enabled require the entitlement data.integration.test, which was not being added as part of our test data bootstrap for new environments. This means our ADO pipelines will fail for environments where this entitlement is not manually added for the integration tester.

What is the current behavior?

  • no patch API implemented for bulk ACL updates

What is the new/expected behavior?

  • patch API implemented for bulk ACL updates

Have you added/updated Unit Tests and Integration Tests?

  • N/A

Any other useful information

Relates to #10 (closed) and #18 (closed)

Edited Dec 17, 2020 by Jason
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: azure-implementing-metadata-patch-api