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 21
    • Merge requests 21
  • 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
  • Issues
  • #72
Closed
Open
Issue created May 20, 2021 by An Ngo@ango2Developer

[Storage] Validate record parent versions in the ancestry block

When a derived record is created, validate that the provided parent record exists, including the version.

Use cases:

GIVEN an otherwise valid record to be PUT into storage that has an ancestry block with a parent ID: parent version AND the record has a valid (existing) record ID but an invalid record version (that version does not exist) WHEN the record is "PUT" into Storage THEN an error is thrown indicating that the ancestry block is invalid due to an invalid record version

GIVEN a correct record to be PUT into storage that has an ancestry block with a parent ID: parent version AND the record has a valid (existing) record ID and a valid record version WHEN the record is "PUT" into Storage THEN the response indicates the record is stored properly (2xx)

Assignee
Assign to
Time tracking