Uploaded image for project: 'Policy Framework'
  1. Policy Framework
  2. POLICY-3368

Revise Rest API conventions and structure

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Medium Medium
    • London Release
    • None
    • clamp
    • None

      Prompted by comments received in code review for a new commissioning endpoint, a review of the conventions and structure of the controllers code is in order.

      Comments included:

      "In PAP & API components, we have kept name & version of entities as path param instead. But I see in this file, other api's are also using query param. Not sure if we want to have a common approach."

      and

      "shouldn't these new urls follow the same convention as api and pap (ie. policy/api/v1/..) to meet the semantic versioning criteria? They probably should if moving it from poc to core capability in this release."

       

      Include the endpoints from the Kubernetes participant in this work

            Unassigned Unassigned
            saul.gill Saul Gill
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: