Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • I Ingestion Framework
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • 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
    • Terraform modules
  • 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
  • #35
Closed
Open
Issue created Feb 24, 2021 by Alan Henson@alan.hensonDeveloper

ADR: Deprecate Ingestion Framework for R3

Status

  • Proposed
  • Trialing
  • Under Review
  • Approved
  • Retired

Context

  • Currently, the Ingestion Framework is only leveraged by the manifest ingestion workflow
  • In previous versions of the Ingestion Framework, pre-pass validation occurred
  • In the current version, pre-pass validation is moved to the manifest ingestion DAG workflow
  • The Ingestion Framework is now a passthrough to the Workflow Service that initiates the manifest ingestion workflow
  • No additional operations are performed by the Ingestion Framework

Scope

  • For the purposes of R3, deprecate the Ingestion Framework endpoints
  • Remove the tests from the automated testing process to prevent Ingestion Framework failures from reflecting against R3
  • OSDU Platform implementers can keep the Ingestion Framework in place if they desire, but it will not be a part of the official Release 3 implementation

Decision

  • To deprecate the Ingestion Framework API endpoints for R3
  • Remove test cases from automated testing for the Ingestion Framework

Rationale

  • Lack of meaningful functionality within the Ingestion Framework should take it out of the critical path for Release 3

Consequences

  • Any existing services or postman collections that leverage the Ingestion Framework endpoints may only work on some implementations
  • Any code that leverages the Ingestion Framework to initiate a manifest ingestion workflow will need to switch to leverage the Workflow Service
Assignee
Assign to
Time tracking