Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • I Ingestion Workflow
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 41
    • Issues 41
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 7
    • Merge requests 7
  • 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 Workflow
  • Issues
  • #105
Closed
Open
Issue created Mar 22, 2021 by Aalekh Jain@aalekhjMaintainer

GET /v1/workflow/{workflow_name}/workflowRun getAllRunInstances parameters

  1. Please specify the expected behaviour from the following parameters present in the api spec for get all run instances of a workflow
  • [boolean] partial
  • [string] conf
  1. What is the expected format in which the start date and end date is provided. Is it going to be Unix epoch time? In case it's going to be unix epoch time, maybe it's better to name it startTimeStamp rather than startDate and endTimeStamp rather than endDate. A minor nit, the type of endDate is mentioned as boolean in the api spec. Should be string.

  2. Currently, the response only returns the list of workflow runs and the cursor for the subsequent requests is not being returned. In such a scenario, how can one obtain the cursor for the subsequent request. Shouldn't we pass the cursor as part of the response? How do we plan to handle this scenario?

  3. What is the expected behaviour when an invalid parameter is passed (apart from limit, cursor, startDate, endDate etc.)?

cc: @kibattul

Edited Apr 01, 2021 by Aalekh Jain
Assignee
Assign to
Time tracking