Uploaded image for project: 'Dev - Nexus Repo'
  1. Dev - Nexus Repo
  2. NEXUS-14639

Add sha1 to asset resource on REST API

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.7.0
    • Component/s: REST
    • Labels:

      Description

      One outcome of NEXUS-14631, all agreed that sha1 (a universal attribute on all formats) should be part of the asset resource response in the API

      Acceptance

      • Add checksum to asset resource (AssetXO)
      • Should apply to /components, /assets, and /search

        Attachments

          Issue Links

          is duplicated by

          Improvement - An improvement or enhancement to an existing feature or task. NEXUS-13553 expose the actual sha1 for an asset via REST without requiring client download of that asset

          • Major - Major loss of function.
          • Closed
          is related to

          Improvement - An improvement or enhancement to an existing feature or task. NEXUS-14631 Add more attributes to REST resource for asset

          • Major - Major loss of function.
          • Closed
          mentioned in

          Page Loading...

            Activity

              People

              Assignee:
              cpeters Collin Peters
              Reporter:
              cpeters Collin Peters
              Last Updated By:
              Peter Lynch Peter Lynch
              Team:
              Nexus - Core
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Date of First Response:

                  tigCommentSecurity.panel-title