packages/google-identity-accesscontextmanager/README.md
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
Access Context Manager 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:
npm install @google-cloud/access-context-manager
Samples are in the samples/ directory. Each sample's README.md has instructions for running its sample.
| Sample | Source Code |
|---|---|
| commit service perimeters | source code |
| create access level | source code |
| create access policy | source code |
| create gcp user access binding | source code |
| create service perimeter | source code |
| delete access level | source code |
| delete access policy | source code |
| delete gcp user access binding | source code |
| delete service perimeter | source code |
| get access level | source code |
| get access policy | source code |
| get gcp user access binding | source code |
| get iam policy | source code |
| get service perimeter | source code |
| list access levels | source code |
| list access policies | source code |
| list gcp user access bindings | source code |
| list service perimeters | source code |
| replace access levels | source code |
| replace service perimeters | source code |
| set iam policy | source code |
| test iam permissions | source code |
| update access level | source code |
| update access policy | source code |
| update gcp user access binding | source code |
| update service perimeter | source code |
| identity | source code |
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:
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/access-context-manager@legacy-8 installs client libraries
for versions compatible with Node.js 8.
This library follows Semantic Versioning.
More Information: Google Cloud Platform Launch Stages
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.
Apache Version 2.0
See LICENSE