This library is considered to be in preview. This means it is still a work-in-progress and under active development. Any release is subject to backwards-incompatible changes at any time.
Config Delivery 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:
- Select or create a Cloud Platform project.
- Enable billing for your project.
- Enable the Config Delivery API API.
- Set up authentication so you can access the API from your local workstation.
npm install @google-cloud/configdeliverySamples are in the samples/ directory. Each sample's README.md has instructions for running its sample.
| Sample | Source Code |
|---|---|
| abort rollout | source code |
| create fleet package | source code |
| create release | source code |
| create resource bundle | source code |
| create variant | source code |
| delete fleet package | source code |
| delete release | source code |
| delete resource bundle | source code |
| delete variant | source code |
| get fleet package | source code |
| get release | source code |
| get resource bundle | source code |
| get rollout | source code |
| get variant | source code |
| list fleet packages | source code |
| list releases | source code |
| list resource bundles | source code |
| list rollouts | source code |
| list variants | source code |
| resume rollout | source code |
| suspend rollout | source code |
| update fleet package | source code |
| update release | source code |
| update resource bundle | source code |
| update variant | source code |
| cloud | source code |
| abort rollout | source code |
| create fleet package | source code |
| create release | source code |
| create resource bundle | source code |
| create variant | source code |
| delete fleet package | source code |
| delete release | source code |
| delete resource bundle | source code |
| delete variant | source code |
| get fleet package | source code |
| get release | source code |
| get resource bundle | source code |
| get rollout | source code |
| get variant | source code |
| list fleet packages | source code |
| list releases | source code |
| list resource bundles | source code |
| list rollouts | source code |
| list variants | source code |
| resume rollout | source code |
| suspend rollout | source code |
| update fleet package | source code |
| update release | source code |
| update resource bundle | source code |
| update variant | source code |
| cloud | source code |
| abort rollout | source code |
| create fleet package | source code |
| create release | source code |
| create resource bundle | source code |
| create variant | source code |
| delete fleet package | source code |
| delete release | source code |
| delete resource bundle | source code |
| delete variant | source code |
| get fleet package | source code |
| get release | source code |
| get resource bundle | source code |
| get rollout | source code |
| get variant | source code |
| list fleet packages | source code |
| list releases | source code |
| list resource bundles | source code |
| list rollouts | source code |
| list variants | source code |
| resume rollout | source code |
| suspend rollout | source code |
| update fleet package | source code |
| update release | source code |
| update resource bundle | source code |
| update variant | source code |
| cloud | source code |
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/configdelivery@legacy-8 installs client libraries
for versions compatible with Node.js 8.
This library follows Semantic Versioning.
More Information: Google Cloud Platform Launch Stages
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.
Apache Version 2.0
See LICENSE