Entity identifier. May span multiple URL path segments.
Format depends on type:
Non-artifact types (e.g. gitCommit, languageModel):
typically a single segment. Allowed characters: [-_.A-Za-z0-9].
artifact — repo-relative path to the file, including nested folders and
the file name. Repository key is not part of id (pass it as ?repo=).
Lead subject = {repo}/{id}.
- Examples:
file.txt, com/acme/service/1.2.3/service-1.2.3.jar
- Rejected: leading
/, trailing /, empty segments (//), . or .. segments
package-version — {name}/versions/{version}. Split on the last
literal /versions/. Package type comes from ?repo= (repo config), not from
the id. {name} shape matches Artifactory leadFile for that package family:
- Maven:
groupId:artifactId — org.apache.tomcat:catalina/versions/9.0.0
- npm (incl. scope):
@myorg/widget/versions/2.0.1
- Docker/OCI:
library/nginx/versions/1.27.0
- Go:
github.com/acme/mod/versions/v1.2.3
- RPM:
httpd/versions/2.4.51-1.el8
- Terraform module:
hashicorp/consul/aws/versions/0.11.0
- PyPI / NuGet / Helm / Debian / Gems / Cargo / etc.:
{pkgName}/versions/{version}
URL-encode : and @ as needed; / remains path structure.
application-version — exactly two segments: {applicationKey}/{version}.
Neither segment may contain /. Example: orders-app/2.4.0.
Lead: {project-}application-versions/{applicationKey}/{version}/release-bundle.json.evd.
release-bundle-version — exactly two segments: {bundleName}/{version}.
Neither segment may contain /. Example: my-release/1.0.0.
Lead: {project-}release-bundles-v2/{bundleName}/{version}/release-bundle.json.evd.
build-version — two or three segments:
{buildName}/{buildNumber} or {buildName}/{buildNumber}/{buildTimestamp}.
buildName / buildNumber must not contain /. Optional buildTimestamp is
digits only (≤ 64). Omitting timestamp resolves to the latest matching build-info
file at request time. Examples: commons-build/1.0.0,
commons-build/1.0.0/1712345678901.
