Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • D Documentation
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 27
    • Issues 27
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1
    • Merge requests 1
  • 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
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Open Subsurface Data Universe SoftwareOpen Subsurface Data Universe Software
  • Documentation
  • Issues
  • #65
Closed
Open
Issue created Mar 23, 2020 by Ferris Argyle@fargyleMaintainer1 of 5 checklist items completed1/5 checklist items

File service - incorporate Delivery service functionality

Status

  • Proposed
  • Trialing
  • Under review
  • Approved
  • Retired

Context & Scope

The Delivery service was intended as a general-purpose delivery mechanism for OSDU assets; in R2, the only assets being delivered are files.

The proposal is to incorporate the additional file delivery methods required into the File service, and push a more general Delivery service to R3.

Details

  • Add a method to the FileService to retrieve the signedURL for a Manifest file, postponing the need for a Delivery Service until R3 or beyond when processing non-file based data, and simplifying the client application calls
  • Originally the unsigned to signedURL conversion was supposed to be in the Delivery service.

Decision

Rationale

Consequences

Implementation Task:

  • Gap fit on this use case
  • Test according to the definition of done (Write test cases)
  • Add a user story to the project ADO

When to revisit


Tradeoff Analysis - Input to decision

Alternatives and implications

Implement Delivery service as designed

  • More complex implementation
  • More future-proof, gets us closer to R3

Postpone Delivery service to R3, and include file delivery requirements in File Service

  • Simpler implementation
  • More complex File service which includes methods which aren't required by some services (eg. Ingestion)

Decision criteria and tradeoffs

Decision timeline

Edited Mar 23, 2020 by Ferris Argyle
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking