Artifact Registry API: Nodejs Client
This library is considered to be stable. The code surface will not change in backwards-incompatible ways unless absolutely necessary (e.g. because of critical security issues) or with an extensive deprecation period. Issues and requests against stable libraries are addressed with the highest priority
Artifact Registry API client for Node.js
A comprehensive list of changes in each version may be found in the CHANGELOG.
Read more about the client libraries for Cloud APIs, including the older Google APIs Client Libraries, in Client Libraries Explained.
Table of contents:
Quickstart
Before you begin
- Select or create a Cloud Platform project.
- Enable billing for your project.
- Enable the Artifact Registry API API.
- Set up authentication so you can access the API from your local workstation. ### Installing the client library
npm install @google-cloud/artifact-registry
Samples
Samples are in the samples/ directory. Each sample's README.md has instructions for running its sample.
| Sample | Source Code |
|---|---|
| batch delete versions | source code |
| create attachment | source code |
| create repository | source code |
| create rule | source code |
| create tag | source code |
| delete attachment | source code |
| delete file | source code |
| delete package | source code |
| delete repository | source code |
| delete rule | source code |
| delete tag | source code |
| delete version | source code |
| get attachment | source code |
| get docker image | source code |
| get file | source code |
| get iam policy | source code |
| get maven artifact | source code |
| get npm package | source code |
| get package | source code |
| get project settings | source code |
| get python package | source code |
| get repository | source code |
| get rule | source code |
| get tag | source code |
| get v p c s c config | source code |
| get version | source code |
| import apt artifacts | source code |
| import yum artifacts | source code |
| list attachments | source code |
| list docker images | source code |
| list files | source code |
| list maven artifacts | source code |
| list npm packages | source code |
| list packages | source code |
| list python packages | source code |
| list repositories | source code |
| list rules | source code |
| list tags | source code |
| list versions | source code |
| set iam policy | source code |
| test iam permissions | source code |
| update file | source code |
| update package | source code |
| update project settings | source code |
| update repository | source code |
| update rule | source code |
| update tag | source code |
| update v p c s c config | source code |
| update version | source code |
| devtools | source code |
| create repository | source code |
| create tag | source code |
| delete package | source code |
| delete repository | source code |
| delete tag | source code |
| delete version | source code |
| get file | source code |
| get iam policy | source code |
| get package | source code |
| get project settings | source code |
| get repository | source code |
| get tag | source code |
| get version | source code |
| import apt artifacts | source code |
| import yum artifacts | source code |
| list files | source code |
| list packages | source code |
| list repositories | source code |
| list tags | source code |
| list versions | source code |
| set iam policy | source code |
| test iam permissions | source code |
| update project settings | source code |
| update repository | source code |
| update tag | source code |
| devtools | source code |
Supported Node.js Versions
Our client libraries follow the Node.js release schedule. Libraries are compatible with all current active and maintenance versions of Node.js. If you are using an end-of-life version of Node.js, we recommend that you update as soon as possible to an actively supported LTS version.
Google's client libraries support legacy versions of Node.js runtimes on a best-efforts basis with the following warnings:
- Legacy versions are not tested in continuous integration.
- Some security patches and features cannot be backported.
- Dependencies cannot be kept up-to-date.
Client libraries targeting some end-of-life versions of Node.js are available, and
can be installed through npm dist-tags.
The dist-tags follow the naming convention legacy-(version).
For example, npm install @google-cloud/artifact-registry@legacy-8 installs client libraries
for versions compatible with Node.js 8.
Versioning
This library follows Semantic Versioning.
More Information: Google Cloud Platform Launch Stages
Contributing
Contributions welcome! See the Contributing Guide.
Please note that this README.md
and a variety of configuration files in this repository (including .nycrc and tsconfig.json)
are generated from a central template.
License
Apache Version 2.0
See LICENSE