Service Usage: Node.js Client

release level npm version

Serviceusage 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 Service Usage API.
  4. Set up authentication with a service account so you can access the API from your local workstation.

Installing the client library

npm install @google-cloud/service-usage

Using the client library

// Imports the Google Cloud client library
const {ServiceUsageClient} = require('@google-cloud/service-usage');

// const parent = 'projects/my-project', // Project to list service usage for.
// filter = 'state:ENABLED' // Filter when listing services.

// Creates a client
const client = new ServiceUsageClient();
async function listServices() {
  for await (const service of client.listServicesAsync({
    parent,
    filter,
  })) {
    console.info(service.name);
  }
}
listServices();

Samples

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

SampleSource CodeTry it
Service_usage.batch_enable_servicessource codeOpen in Cloud Shell
Service_usage.batch_get_servicessource codeOpen in Cloud Shell
Service_usage.disable_servicesource codeOpen in Cloud Shell
Service_usage.enable_servicesource codeOpen in Cloud Shell
Service_usage.get_servicesource codeOpen in Cloud Shell
Service_usage.list_servicessource codeOpen in Cloud Shell
Service_usage.batch_enable_servicessource codeOpen in Cloud Shell
Service_usage.create_admin_overridesource codeOpen in Cloud Shell
Service_usage.create_consumer_overridesource codeOpen in Cloud Shell
Service_usage.delete_admin_overridesource codeOpen in Cloud Shell
Service_usage.delete_consumer_overridesource codeOpen in Cloud Shell
Service_usage.disable_servicesource codeOpen in Cloud Shell
Service_usage.enable_servicesource codeOpen in Cloud Shell
Service_usage.generate_service_identitysource codeOpen in Cloud Shell
Service_usage.get_consumer_quota_limitsource codeOpen in Cloud Shell
Service_usage.get_consumer_quota_metricsource codeOpen in Cloud Shell
Service_usage.get_servicesource codeOpen in Cloud Shell
Service_usage.import_admin_overridessource codeOpen in Cloud Shell
Service_usage.import_consumer_overridessource codeOpen in Cloud Shell
Service_usage.list_admin_overridessource codeOpen in Cloud Shell
Service_usage.list_consumer_overridessource codeOpen in Cloud Shell
Service_usage.list_consumer_quota_metricssource codeOpen in Cloud Shell
Service_usage.list_servicessource codeOpen in Cloud Shell
Service_usage.update_admin_overridesource codeOpen in Cloud Shell
Service_usage.update_consumer_overridesource codeOpen in Cloud Shell
Quickstartsource codeOpen in Cloud Shell
Quickstartsource codeOpen in Cloud Shell

The Service Usage Node.js Client API Reference documentation also contains samples.

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/service-usage@legacy-8 installs client libraries for versions compatible with Node.js 8.

Versioning

This library follows Semantic Versioning.

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.

More Information: Google Cloud Platform Launch Stages

Contributing

Contributions welcome! See the Contributing Guide.

Please note that this README.md, the samples/README.md, and a variety of configuration files in this repository (including .nycrc and tsconfig.json) are generated from a central template. To edit one of these files, make an edit to its templates in directory.

License

Apache Version 2.0

See LICENSE