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

Improve Manifest RESTful API endpoints

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • None
    • None
    • 5
    • sst_container_tools
    • RUN 211, RUN 212, RUN 213

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

       

      The other libpod resources provide an attribute Id. Operations on resources can use these Ids to uniquely identify the resource. Manifests do not expose an Id for operations to use. Instead manifest operations require the client to use the Name under which the given Manifest was resource created. Id should be supported.

       

      The status code of 500 is  returned on bad input, rather than 400.

       

            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: