Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • W Waarp Gateway
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 48
    • Issues 48
    • List
    • Boards
    • Service Desk
    • Milestones
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Applications
  • Waarp Gateway
  • Waarp Gateway
  • Issues
  • #153
Closed
Open
Issue created Aug 20, 2020 by Bruno Carlin@bruno.carlinOwner

Update commands should only update what is set to change

Even if the REST API does not support partial updates (PATCH), the comand line client should allow one to do partial updates (it can get the actual record and update it).

For example :

$ waarp-gateway [...] server update sftp_iface 
json: error calling MarshalJSON for type json.RawMessage: unexpected end of JSON input

Should not return an error, but print nothing to do.

$ waarp-gateway [...] server update sftp_iface -c '{"address":"0.0.0.0","port":2222}'
unknown protocol

should update only the config and not the protocol.

Actually, there is an inconsistency between arguments verification and the outcome: if an argument is optional, there should be no error when it is omitted.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking