Binary artifact
Binary artifact is a file containing any type of package, e.g., an installation script, an executable, a CSV file, a document, an image, etc. A binary artifact package always contains exactly one file.
In the registry, any binary artifact is defined by the <artifact_name>/<artifact_version> pair and stored at <registry_URL>/<artifact_name>/<artifact_version>/<file_name>. For example:
https://registry.yandexcloud.net/binaries/cn15fqbr806r********/sample-package/3.5.4/agent-installer.sh
Note
The binary artifact version must follow the SemVer format: it must consist of three non-negative integers separated by dots (major.minor.patch). You can optionally append a plus sign (+) followed by dot-separated version IDs.
Examples of versions:
1.0.01.2.3+first4.5.6+first.second7.8.9+first-----with-long-idf
You can push and pull a binary artifact using HTTP requests with IAM token authentication.
You can delete a binary artifact from the management console. You cannot overwrite the existing version of a binary artifact.