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
Certificate Manager 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 Certificate Manager API API.
- Set up authentication so you can access the API from your local workstation.
npm install @google-cloud/certificate-managerSamples are in the samples/ directory. Each sample's README.md has instructions for running its sample.
| Sample | Source Code |
|---|---|
| create certificate | source code |
| create certificate issuance config | source code |
| create certificate map | source code |
| create certificate map entry | source code |
| create dns authorization | source code |
| create trust config | source code |
| delete certificate | source code |
| delete certificate issuance config | source code |
| delete certificate map | source code |
| delete certificate map entry | source code |
| delete dns authorization | source code |
| delete trust config | source code |
| get certificate | source code |
| get certificate issuance config | source code |
| get certificate map | source code |
| get certificate map entry | source code |
| get dns authorization | source code |
| get trust config | source code |
| list certificate issuance configs | source code |
| list certificate map entries | source code |
| list certificate maps | source code |
| list certificates | source code |
| list dns authorizations | source code |
| list trust configs | source code |
| update certificate | source code |
| update certificate map | source code |
| update certificate map entry | source code |
| update dns authorization | source code |
| update trust config | 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/certificate-manager@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