Secret Manager: Node.js Client
Secrets client for Node.js
A comprehensive list of changes in each version may be found in the 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 older Google APIs Client Libraries, in Client Libraries Explained .
Table of contents:
Quickstart
Before you begin
- Select or create a Cloud Platform project .
- Enable billing for your project .
- Enable the Secret Manager API .
- 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/secret-manager
Using the client library
// Import the Secret Manager client and instantiate it:
const {SecretManagerServiceClient} = require(' @google-cloud/secret-manager
');
const client = new SecretManagerServiceClient
();
/**
* 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 the samples/
directory. Each sample's README.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 | ![]() |
The Secret Manager 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.
Client libraries targeting some end-of-life versions of Node.js are available, and
can be installed via npm dist-tags
.
The dist-tags follow the naming convention legacy-(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 versions compatible with Node.js 8.
Versioning
This library follows Semantic Versioning .
This library is considered to be General Availability (GA). This means it is 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 GAlibraries 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 template in this directory
.
License
Apache Version 2.0
See LICENSE