Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • I Ingestion Framework
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 5
    • Issues 5
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • 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
  • Data Flow
  • Data IngestionData Ingestion
  • Ingestion Framework
  • Issues
  • #30
Closed
Open
Issue created Jan 14, 2021 by Dmitriy Rudko@Dmitriy_RudkoOwner

ADR: Ingestion Service - R3 Schema support

Context

  • Data Loading requirements to enforce validation of users request before pass control to DAG logic.
  • Currently all validation logic implemented in DAG itself.
  • It was decided to do this work post-R3, but still will keep Ingestion Service in R3 architecture as an entry point for Ingestion.
  • To work with R3, Ingestion Service endpoints should be updated to support R3 schemas /submitWithManifest.

Scope

  • Add a new endpoint /api/v2/submit/manifest that will support R3 Manifest format.
  • Update Ingestion Service logic to work with updated API of Workflow service (see ADR ???)
  • See OpenAPI Spec for details

Decision

  • Introduce a new endpoint
  • Code change in Ingestion Service > Core to work with updated API of Workflow service

Rationale

  • Required change for E2E R3 Ingestion

Consequences

  • Work will be done by GCP
  • Most of the changes will be done is Ingestion Service > Core
  • No CSPs involvement required as there is not SPI layer in Ingestion service

When to revisit

  • Post R3
Assignee
Assign to
Time tracking