Internet Explorer is no longer supported. Many things will still work, but your experience will be degraded and some things won't function. Please use a modern browser such as Edge, Chrome, or Firefox.

Get Asset Metadata

view on GitHub

Get Asset Metadata is available as both a pgutil command and an HTTP Request, and will return metadata for the specified asset "item" (file or folder) as a JSON AssetDirectoryItem object

Command Specification (CLI)

The assets metadata get command is used to return metadata for the specified asset item.

The --path option is always required. The --feed option is required if there is no default feed configured.

Getting asset metadata requires the asset directory (e.g. MyAssetDirectory) and asset path (e.g. data-files/data.bin):

pgutil assets metadata get --path=data-files/data.bin --feed=myAssetDirectory

Running the command will return metadata of the specified asset:

Name: example.txt
Size: 4
Type: http://proget.corp.local/endpoints/myAssetDirectory/content/data-files/example.txt
Created: 6/5/2024 3:29:14 PM
Modified: 6/5/2024 3:29:14 PM
Caching: TTL (60 seconds)

-- Hashes --
MD5: 098f6bcd4621d373cade4e832627b4f6
SHA1: a94a8fe5ccb19ba61c4c0873d391e987982fbbd3
SHA256: 9f86d081884c7d659a2feaa0c55ad015a3bf4f1b2b0b822cd15d6c15b0f00a08
SHA512: ee26b0dd4af7e749aa1a8ee3c10ae9923f618980772e473f8819a5d4940e0db27ac185f8a0e1d5f84f88bc887fd67b143732c304cc5fa9ad8e6f57f50028a8ff

-- Custom Metadata --
myKey1: myValue1
myKey2: myValue2

HTTP Request Specification

To get the metadata of an item, simply GET to the URL with the AssetDirectoryName and path to the item.

GET /endpoints/«AssetDirectoryName»/metadata/«path»

HTTP Response Specification

A successful (200) response body will contain a AssetDirectoryItem object describing a file or folder in the specified path. For example, querying example.txt, the request would return a single object:

{
  "name": "example.txt",
  "parent": "folder",
  "size": 4,
  "type": "text/plain",
  "content": "http://proget.corp.local/endpoints/myAssetDirectory/content/data-files/example.txt",
  "md5": "098f6bcd4621d373cade4e832627b4f6",
  "sha1": "a94a8fe5ccb19ba61c4c0873d391e987982fbbd3",
  "sha256": "9f86d081884c7d659a2feaa0c55ad015a3bf4f1b2b0b822cd15d6c15b0f00a08",
  "sha512": "ee26b0dd4af7e749aa1a8ee3c10ae9923f618980772e473f8819a5d4940e0db27ac185f8a0e1d5f84f88bc887fd67b143732c304cc5fa9ad8e6f57f50028a8ff",
  "created": "2024-06-05T06:29:14.277Z",
  "modified": "2024-06-10T02:20:53.87Z",
  "userMetadata": {
    "myKey": "myValue"
  },
  "cacheHeader": {
    "type": "TTL",
    "value": 60
  }
}
Response Details
200 (Success) the body will contain a AssetDirectoryItem object
401 (Authentication Required) indicates a missing, unknown, or unauthorized API Key
404 (Item not Found) indicates that the file or folder does not exist