Several endpoints require the use of a Component ID which must be formatted, according to its package type, using the convention described in the following table:
Package Type | Identifier | Example |
---|---|---|
Maven |
|
|
Docker and OCI |
|
|
RPM |
|
|
Debian |
|
|
NuGet |
|
|
Generic file |
|
|
NPM |
|
|
Python |
|
|
Composer |
|
|
Golang |
|
|
Alpine |
|
|
Conan |
|
|
Conda |
|
|
CRAN |
|
|
Cargo |
|
|
Hugging Face ML |
|
|
Terraform state | For Terraform state use the generic file identifier |
|
In addition Build, Release Bundle, and Release Bundle V2 have dedicated identifiers:
Resource Type | Identifier | Example |
---|---|---|
Build Version |
It’s required if the build is in a Project scope. |
|
Release Bundle Version |
|
|
Release Bundle V2 Version |
|
|