OS Config API: Node.js Client

release level npm version

Osconfig 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 the OS Config API API.
  3. 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/os-config

Using the client library

// Imports the Google Cloud client library
const {OsConfigServiceClient} = require('@google-cloud/os-config');

// Creates a client
const client = new OsConfigServiceClient();

// project = 'my-project' // Project to list deployments for.

async function listPatchDeployments() {
  const [deployments] = await client.listPatchDeployments({
    parent: `projects/${project}`,
  });
  console.info(`found ${deployments.length} deployments:`);
  console.info(deployments);
}
const listPatchDeploymentsResponse = listPatchDeployments();

Samples

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

SampleSource CodeTry it
Os_config_service.cancel_patch_jobsource codeOpen in Cloud Shell
Os_config_service.create_patch_deploymentsource codeOpen in Cloud Shell
Os_config_service.delete_patch_deploymentsource codeOpen in Cloud Shell
Os_config_service.execute_patch_jobsource codeOpen in Cloud Shell
Os_config_service.get_patch_deploymentsource codeOpen in Cloud Shell
Os_config_service.get_patch_jobsource codeOpen in Cloud Shell
Os_config_service.list_patch_deploymentssource codeOpen in Cloud Shell
Os_config_service.list_patch_job_instance_detailssource codeOpen in Cloud Shell
Os_config_service.list_patch_jobssource codeOpen in Cloud Shell
Os_config_service.pause_patch_deploymentsource codeOpen in Cloud Shell
Os_config_service.resume_patch_deploymentsource codeOpen in Cloud Shell
Os_config_service.update_patch_deploymentsource codeOpen in Cloud Shell
Os_config_zonal_service.create_o_s_policy_assignmentsource codeOpen in Cloud Shell
Os_config_zonal_service.delete_o_s_policy_assignmentsource codeOpen in Cloud Shell
Os_config_zonal_service.get_inventorysource codeOpen in Cloud Shell
Os_config_zonal_service.get_o_s_policy_assignmentsource codeOpen in Cloud Shell
Os_config_zonal_service.get_o_s_policy_assignment_reportsource codeOpen in Cloud Shell
Os_config_zonal_service.get_vulnerability_reportsource codeOpen in Cloud Shell
Os_config_zonal_service.list_inventoriessource codeOpen in Cloud Shell
Os_config_zonal_service.list_o_s_policy_assignment_reportssource codeOpen in Cloud Shell
Os_config_zonal_service.list_o_s_policy_assignment_revisionssource codeOpen in Cloud Shell
Os_config_zonal_service.list_o_s_policy_assignmentssource codeOpen in Cloud Shell
Os_config_zonal_service.list_vulnerability_reportssource codeOpen in Cloud Shell
Os_config_zonal_service.update_o_s_policy_assignmentsource codeOpen in Cloud Shell
Os_config_zonal_service.create_o_s_policy_assignmentsource codeOpen in Cloud Shell
Os_config_zonal_service.delete_o_s_policy_assignmentsource codeOpen in Cloud Shell
Os_config_zonal_service.get_instance_o_s_policies_compliancesource codeOpen in Cloud Shell
Os_config_zonal_service.get_inventorysource codeOpen in Cloud Shell
Os_config_zonal_service.get_o_s_policy_assignmentsource codeOpen in Cloud Shell
Os_config_zonal_service.get_o_s_policy_assignment_reportsource codeOpen in Cloud Shell
Os_config_zonal_service.get_vulnerability_reportsource codeOpen in Cloud Shell
Os_config_zonal_service.list_instance_o_s_policies_compliancessource codeOpen in Cloud Shell
Os_config_zonal_service.list_inventoriessource codeOpen in Cloud Shell
Os_config_zonal_service.list_o_s_policy_assignment_reportssource codeOpen in Cloud Shell
Os_config_zonal_service.list_o_s_policy_assignment_revisionssource codeOpen in Cloud Shell
Os_config_zonal_service.list_o_s_policy_assignmentssource codeOpen in Cloud Shell
Os_config_zonal_service.list_vulnerability_reportssource codeOpen in Cloud Shell
Os_config_zonal_service.update_o_s_policy_assignmentsource codeOpen in Cloud Shell
Os_config_service.cancel_patch_jobsource codeOpen in Cloud Shell
Os_config_service.create_guest_policysource codeOpen in Cloud Shell
Os_config_service.create_patch_deploymentsource codeOpen in Cloud Shell
Os_config_service.delete_guest_policysource codeOpen in Cloud Shell
Os_config_service.delete_patch_deploymentsource codeOpen in Cloud Shell
Os_config_service.execute_patch_jobsource codeOpen in Cloud Shell
Os_config_service.get_guest_policysource codeOpen in Cloud Shell
Os_config_service.get_patch_deploymentsource codeOpen in Cloud Shell
Os_config_service.get_patch_jobsource codeOpen in Cloud Shell
Os_config_service.list_guest_policiessource codeOpen in Cloud Shell
Os_config_service.list_patch_deploymentssource codeOpen in Cloud Shell
Os_config_service.list_patch_job_instance_detailssource codeOpen in Cloud Shell
Os_config_service.list_patch_jobssource codeOpen in Cloud Shell
Os_config_service.lookup_effective_guest_policysource codeOpen in Cloud Shell
Os_config_service.pause_patch_deploymentsource codeOpen in Cloud Shell
Os_config_service.resume_patch_deploymentsource codeOpen in Cloud Shell
Os_config_service.update_guest_policysource codeOpen in Cloud Shell
Os_config_service.update_patch_deploymentsource codeOpen in Cloud Shell
Quickstartsource codeOpen in Cloud Shell
Quickstart.testsource codeOpen in Cloud Shell

The OS Config API 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/os-config@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