Uploaded image for project: 'OpenShift Runtimes'
  1. OpenShift Runtimes
  2. RUN-1261

Audit RESTful API endpoints

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • None
    • None
    • 5
    • sst_container_tools

      As a developer, I want a consistent and easy to use RESTful API following the "principle of least surprise".

       

      Audit RESTful endpoints for:

      • Consistent (libpod) or Compatible (compat) HTTP return codes
      • Improved messaging
        • No more "Something bad happened" messages
      • Should returned JSON continue to be HTML encoded?
      • Provide references to allow detailed documentation for all fields
      • Consistent input/output
        • single input  should not result in a collection output
        • Content-Type header set to payload contents
      • Flag unused types and references currently defined in swagger

      Card should result in cards detailed needed changes.

       

      Associated Cards:

            jhonce@redhat.com Jhon Honce
            jhonce@redhat.com Jhon Honce
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: