Back to Google Cloud Node

[VMware Engine API: Nodejs Client][homepage]

packages/google-cloud-vmwareengine/README.md

0.57.019.2 KB
Original Source

VMware Engine 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

VMware Engine 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

  1. Select or create a Cloud Platform project.
  2. Enable billing for your project.
  3. Enable the VMware Engine API API.
  4. Set up authentication so you can access the API from your local workstation.

Installing the client library

bash
npm install @google-cloud/vmwareengine

Samples

Samples are in the samples/ directory. Each sample's README.md has instructions for running its sample.

SampleSource Code
cloudsource code
create clustersource code
create external access rulesource code
create external addresssource code
create hcx activation keysource code
create logging serversource code
create management dns zone bindingsource code
create network peeringsource code
create network policysource code
create private cloudsource code
create private connectionsource code
create vmware engine networksource code
delete clustersource code
delete external access rulesource code
delete external addresssource code
delete logging serversource code
delete management dns zone bindingsource code
delete network peeringsource code
delete network policysource code
delete private cloudsource code
delete private connectionsource code
delete vmware engine networksource code
fetch network policy external addressessource code
get clustersource code
get dns bind permissionsource code
get dns forwardingsource code
get external access rulesource code
get external addresssource code
get hcx activation keysource code
get logging serversource code
get management dns zone bindingsource code
get network peeringsource code
get network policysource code
get nodesource code
get node typesource code
get private cloudsource code
get private connectionsource code
get subnetsource code
get vmware engine networksource code
grant dns bind permissionsource code
list clusterssource code
list external access rulessource code
list external addressessource code
list hcx activation keyssource code
list logging serverssource code
list management dns zone bindingssource code
list network peeringssource code
list network policiessource code
list node typessource code
list nodessource code
list peering routessource code
list private cloudssource code
list private connection peering routessource code
list private connectionssource code
list subnetssource code
list vmware engine networkssource code
repair management dns zone bindingsource code
reset nsx credentialssource code
reset vcenter credentialssource code
revoke dns bind permissionsource code
show nsx credentialssource code
show vcenter credentialssource code
undelete private cloudsource code
update clustersource code
update dns forwardingsource code
update external access rulesource code
update external addresssource code
update logging serversource code
update management dns zone bindingsource code
update network peeringsource code
update network policysource code
update private cloudsource code
update private connectionsource code
update subnetsource code
update vmware engine networksource 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/vmwareengine@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