Skip to main content

Synopsis

Retrieves detailed information about a specific artifact or searches for artifacts by name in the Harness Artifact Registry.
hc artifact get [artifact-name] [flags]

Arguments

artifact-name
string
Optional artifact name to search for. If not provided, lists all artifacts.

Options

--registry
string
Filter by registry name
--page-size
integer
default:"10"
Number of items per page
--page
integer
default:"0"
Page number (zero-indexed)

Output Format

The command displays artifact information in a table format with:
  • Artifact - Name of the artifact
  • Version - Version number
  • Package Type - Type of package
  • Registry - Registry identifier
  • Download Count - Download statistics

Examples

hc artifact get nginx --registry docker-registry

Search Behavior

When you provide an artifact name, the command performs a search operation:
  • Partial matches are supported
  • Case-sensitive search
  • Returns all versions matching the search term

Output Example

Artifact    Version  Package Type  Registry         Download Count
nginx       1.21.0   DOCKER        docker-registry  125
nginx       1.20.2   DOCKER        docker-registry  98
nginx       1.19.10  DOCKER        docker-registry  67

Page: 0 | Total Pages: 1 | Total Items: 3

Use Cases

hc artifact get my-app --registry docker-registry
This returns all versions of my-app available in the registry.
hc artifact get library-name
Omit the --registry flag to search across all registries in your account.
hc artifact get package-name --registry npm-registry
Use this to verify an artifact exists before attempting to pull it.
The search uses the artifact name as a search term. If no artifacts match, an empty result set is returned.

See Also

Build docs developers (and LLMs) love