@maxim_mazurok/gapi.client.accesscontextmanager-v1 0.0.20230820 → 0.0.20230903

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/index.d.ts +6 -6
  2. package/package.json +1 -1
  3. package/tests.ts +1 -1
package/index.d.ts CHANGED
@@ -9,7 +9,7 @@
9
9
  // This file was generated by https://github.com/Maxim-Mazurok/google-api-typings-generator. Please do not edit it manually.
10
10
  // In case of any problems please post issue to https://github.com/Maxim-Mazurok/google-api-typings-generator
11
11
  // Generated from: https://accesscontextmanager.googleapis.com/$discovery/rest?version=v1
12
- // Revision: 20230820
12
+ // Revision: 20230903
13
13
 
14
14
  /// <reference types="gapi.client" />
15
15
 
@@ -59,11 +59,11 @@ declare namespace gapi.client {
59
59
  parent?:
60
60
  string;
61
61
  /**
62
- * The scopes of a policy define which resources an ACM policy can restrict, and where ACM resources can be referenced. For example, a policy with scopes=["folders/123"] has the
63
- * following behavior: - vpcsc perimeters can only restrict projects within folders/123 - access levels can only be referenced by resources within folders/123. If empty, there are no
64
- * limitations on which resources can be restricted by an ACM policy, and there are no limitations on where ACM resources can be referenced. Only one policy can include a given scope
65
- * (attempting to create a second policy which includes "folders/123" will result in an error). Currently, scopes cannot be modified after a policy is created. Currently, policies can
66
- * only have a single scope. Format: list of `folders/{folder_number}` or `projects/{project_number}`
62
+ * The scopes of the AccessPolicy. Scopes define which resources a policy can restrict and where its resources can be referenced. For example, policy A with `scopes=["folders/123"]`
63
+ * has the following behavior: - ServicePerimeter can only restrict projects within `folders/123`. - ServicePerimeter within policy A can only reference access levels defined within
64
+ * policy A. - Only one policy can include a given scope; thus, attempting to create a second policy which includes `folders/123` will result in an error. If no scopes are provided,
65
+ * then any resource within the organization can be restricted. Scopes cannot be modified after a policy is created. Policies can only have a single scope. Format: list of
66
+ * `folders/{folder_number}` or `projects/{project_number}`
67
67
  */
68
68
  scopes?:
69
69
  string[];
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@maxim_mazurok/gapi.client.accesscontextmanager-v1",
3
- "version": "0.0.20230820",
3
+ "version": "0.0.20230903",
4
4
  "description": "TypeScript typings for Access Context Manager API v1",
5
5
  "license": "MIT",
6
6
  "author": {
package/tests.ts CHANGED
@@ -3,7 +3,7 @@
3
3
  // This file was generated by https://github.com/Maxim-Mazurok/google-api-typings-generator. Please do not edit it manually.
4
4
  // In case of any problems please post issue to https://github.com/Maxim-Mazurok/google-api-typings-generator
5
5
 
6
- // Revision: 20230820
6
+ // Revision: 20230903
7
7
 
8
8
  gapi.load('client', async () => {
9
9
  /** now we can use gapi.client */