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 8
    • Merge requests 8
  • 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
  • #108
Closed
Open
Issue created Mar 25, 2021 by Monalisa Srivastava@msrivastava

registerCustomOperator API </customOperator> returns success if an empty "properties" block is passed but throws 400 if "properties" block is missing

Tested on AZURE : API : https://{HOST}/api/workflow/v1/customOperator

Hit the API with below payload: { "name": "string", "className": "string", "description": "string", "content": "string", "properties": [

] }
Response : API returns success 200 OK

Now hit the same API with Properties block missing and observe that 400 response code is returned Expected If properties block is mandatory, then empty block should also return 400 instead of 200 and return a message with the exact reason

Assignee
Assign to
Time tracking