Package Exports
- @google-cloud/resource-manager
- @google-cloud/resource-manager/build/protos/protos
- @google-cloud/resource-manager/build/protos/protos.js
- @google-cloud/resource-manager/build/src/index.js
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@google-cloud/resource-manager) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
Cloud Resource Manager API: Nodejs Client
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
Cloud Resource Manager API client for Node.js
Node.js idiomatic client for [Cloud Resource Manager API][product-docs].
Google Cloud Platform provides container resources such as Organizations and Projects, that allow you to group and hierarchically organize other Cloud Platform resources. This hierarchical organization lets you easily manage common aspects of your resources such as access control and configuration settings. The Cloud Resource Manager API enables you to programmatically manage these container resources.
IMPORTANT NOTE
Version 2.0.0 renames @google-cloud/resource to @google-cloud/resource-manager on npm.
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
- Select or create a Cloud Platform project.
- Enable billing for your project.
- Enable the Cloud Resource Manager API API.
- Set up authentication so you can access the API from your local workstation.
Installing the client library
npm install @google-cloud/resource-managerSamples
Samples are in the samples/ directory. Each sample's README.md has instructions for running its sample.
| Sample | Source Code |
|---|---|
| create folder | source code |
| delete folder | source code |
| get folder | source code |
| get iam policy | source code |
| list folders | source code |
| move folder | source code |
| search folders | source code |
| set iam policy | source code |
| test iam permissions | source code |
| undelete folder | source code |
| update folder | source code |
| get iam policy | source code |
| get organization | source code |
| search organizations | source code |
| set iam policy | source code |
| test iam permissions | source code |
| create project | source code |
| delete project | source code |
| get iam policy | source code |
| get project | source code |
| list projects | source code |
| move project | source code |
| search projects | source code |
| set iam policy | source code |
| test iam permissions | source code |
| undelete project | source code |
| update project | source code |
| cloud | source code |
| create tag binding | source code |
| delete tag binding | source code |
| list effective tags | source code |
| list tag bindings | source code |
| create tag hold | source code |
| delete tag hold | source code |
| list tag holds | source code |
| create tag key | source code |
| delete tag key | source code |
| get iam policy | source code |
| get namespaced tag key | source code |
| get tag key | source code |
| list tag keys | source code |
| set iam policy | source code |
| test iam permissions | source code |
| update tag key | source code |
| create tag value | source code |
| delete tag value | source code |
| get iam policy | source code |
| get namespaced tag value | source code |
| get tag value | source code |
| list tag values | source code |
| set iam policy | source code |
| test iam permissions | source code |
| update tag value | source code |
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/resource-manager@legacy-8 installs client libraries
for versions compatible with Node.js 8.
Versioning
This library follows Semantic Versioning.
More Information: Google Cloud Platform Launch Stages
Contributing
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.
License
Apache Version 2.0
See LICENSE