Secret Manager: Node.js Client

Secrets client for Node.js

A comprehensive list of changes in each version may be found inthe CHANGELOG.

• Secret Manager Node.js Client API Reference
• Secret Manager Documentation
• github.com/googleapis/nodejs-secret-manager

Read more about the client libraries for Cloud APIs, including the olderGoogle APIs Client Libraries, inClient Libraries Explained.

Table of contents:

• Quickstart
  • Before you begin
  • Installing the client library
  • Using the client library
• Samples
• Versioning
• Contributing
• License

Quickstart

Before you begin

1. Select or create a Cloud Platform project.
2. Enable billing for your project.
3. Enable the Secret Manager API.
4. Set up authentication with a service account so you can access theAPI from your local workstation.

Installing the client library

npm install @google-cloud/secret-manager

Using the client library

// Import the Secret Manager client and instantiate it:const {SecretManagerServiceClient} = require('@google-cloud/secret-manager');const client = newSecretManagerServiceClient();/** * TODO(developer): Uncomment these variables before running the sample. */// parent = 'projects/my-project', // Project for which to manage secrets.// secretId = 'foo', // Secret ID.// payload = 'hello world!' // String source data.async function createAndAccessSecret() {  // Create the secret with automation replication.  const [secret] = await client.createSecret({    parent: parent,    secret: {      name: secretId,      replication: {        automatic: {},      },    },    secretId,  });  console.info(`Created secret ${secret.name}`);  // Add a version with a payload onto the secret.  const [version] = await client.addSecretVersion({    parent: secret.name,    payload: {      data: Buffer.from(payload, 'utf8'),    },  });  console.info(`Added secret version ${version.name}`);  // Access the secret.  const [accessResponse] = await client.accessSecretVersion({    name: version.name,  });  const responsePayload = accessResponse.payload.data.toString('utf8');  console.info(`Payload: ${responsePayload}`);}createAndAccessSecret();

Samples

Samples are in thesamples/ directory. Each sample'sREADME.md has instructions for running its sample.

Sample	Source Code	Try it
Access Secret Version	source code
Add Secret Version	source code
Create Secret	source code
Delete Secret	source code
Destroy Secret Version	source code
Disable Secret Version	source code
Enable Secret Version	source code
Get Secret	source code
Get Secret Version	source code
Iam Grant Access	source code
Iam Revoke Access	source code
List Secret Versions	source code
List Secrets	source code
Quickstart	source code
Update Secret	source code

TheSecret Manager Node.js Client API Reference documentationalso contains samples.

Supported Node.js Versions

Our client libraries follow theNode.js release schedule.Libraries are compatible with all currentactive andmaintenance versions ofNode.js.

Client libraries targeting some end-of-life versions of Node.js are available, andcan be installed via npmdist-tags.The dist-tags follow the naming conventionlegacy-(version).

Legacy Node.js versions are supported as a best effort:

• Legacy versions will not be tested in continuous integration.
• Some security patches may not be able to be backported.
• Dependencies will not be kept up-to-date, and features will not be backported.

Legacy tags available

• legacy-8: install client libraries from this dist-tag for versionscompatible with Node.js 8.

Versioning

This library followsSemantic Versioning.

This library is considered to beGeneral Availability (GA). This means itis stable; the code surface will not change in backwards-incompatible waysunless absolutely necessary (e.g. because of critical security issues) or withan extensive deprecation period. Issues and requests againstGA librariesare addressed with the highest priority.

More Information:Google Cloud Platform Launch Stages

Contributing

Contributions welcome! See theContributing Guide.

Please note that thisREADME.md, thesamples/README.md,and a variety of configuration files in this repository (including.nycrc andtsconfig.json)are generated from a central template. To edit one of these files, make an editto its templates indirectory.

License

Apache Version 2.0

SeeLICENSE