mirror of
https://github.com/OMGeeky/google-apis-rs.git
synced 2026-02-23 15:49:49 +01:00
Bump version to 1.0.9; update JSON schemas; add new APIs
This commit is contained in:
Sebastian Thiel
@@ -598,7 +598,7 @@
|
||||
}
|
||||
}
|
||||
},
|
||||
"revision": "20190327",
|
||||
"revision": "20190626",
|
||||
"rootUrl": "https://accesscontextmanager.googleapis.com/",
|
||||
"schemas": {
|
||||
"AccessLevel": {
|
||||
@@ -689,6 +689,24 @@
|
||||
},
|
||||
"type": "object"
|
||||
},
|
||||
"BridgeServiceRestriction": {
|
||||
"description": "Alpha. Specifies which services are granted access via this Bridge Service\nPerimeter.",
|
||||
"id": "BridgeServiceRestriction",
|
||||
"properties": {
|
||||
"allowedServices": {
|
||||
"description": "The list of APIs usable through the Bridge Perimeter. Must be empty\nunless 'enable_restriction' is True.",
|
||||
"items": {
|
||||
"type": "string"
|
||||
},
|
||||
"type": "array"
|
||||
},
|
||||
"enableRestriction": {
|
||||
"description": "Whether to restrict the set of APIs callable through the Bridge Service\nPerimeter.",
|
||||
"type": "boolean"
|
||||
}
|
||||
},
|
||||
"type": "object"
|
||||
},
|
||||
"Condition": {
|
||||
"description": "A condition necessary for an `AccessLevel` to be granted. The Condition is an\nAND over its fields. So a Condition is true if: 1) the request IP is from one\nof the listed subnetworks AND 2) the originating device complies with the\nlisted device policy AND 3) all listed access levels are granted AND 4) the\nrequest was sent at a time allowed by the DateTimeRestriction.",
|
||||
"id": "Condition",
|
||||
@@ -796,6 +814,24 @@
|
||||
},
|
||||
"type": "object"
|
||||
},
|
||||
"IngressServiceRestriction": {
|
||||
"description": "Alpha. Specifies how Access Levels are to be used for accessing the Service\nPerimeter.",
|
||||
"id": "IngressServiceRestriction",
|
||||
"properties": {
|
||||
"allowedServices": {
|
||||
"description": "The list of APIs usable with a valid Access Level. Must be empty unless\n'enable_restriction' is True.",
|
||||
"items": {
|
||||
"type": "string"
|
||||
},
|
||||
"type": "array"
|
||||
},
|
||||
"enableRestriction": {
|
||||
"description": "Whether to restrict the set of APIs callable outside the Service\nPerimeter via Access Levels.",
|
||||
"type": "boolean"
|
||||
}
|
||||
},
|
||||
"type": "object"
|
||||
},
|
||||
"ListAccessLevelsResponse": {
|
||||
"description": "A response to `ListAccessLevelsRequest`.",
|
||||
"id": "ListAccessLevelsResponse",
|
||||
@@ -871,7 +907,7 @@
|
||||
"type": "object"
|
||||
},
|
||||
"name": {
|
||||
"description": "The server-assigned name, which is only unique within the same service that\noriginally returns it. If you use the default HTTP mapping, the\n`name` should have the format of `operations/some/unique/name`.",
|
||||
"description": "The server-assigned name, which is only unique within the same service that\noriginally returns it. If you use the default HTTP mapping, the\n`name` should be a resource name ending with `operations/{unique_id}`.",
|
||||
"type": "string"
|
||||
},
|
||||
"response": {
|
||||
@@ -974,6 +1010,14 @@
|
||||
},
|
||||
"type": "array"
|
||||
},
|
||||
"bridgeServiceRestriction": {
|
||||
"$ref": "BridgeServiceRestriction",
|
||||
"description": "Alpha. Configuration for what services are accessible via the Bridge\nPerimeter. Must be empty for non-Bridge Perimeters."
|
||||
},
|
||||
"ingressServiceRestriction": {
|
||||
"$ref": "IngressServiceRestriction",
|
||||
"description": "Alpha. Configuration for which services may be used with Access Levels."
|
||||
},
|
||||
"resources": {
|
||||
"description": "A list of GCP resources that are inside of the service perimeter.\nCurrently only projects are allowed. Format: `projects/{project_number}`",
|
||||
"items": {
|
||||
@@ -994,12 +1038,16 @@
|
||||
"type": "string"
|
||||
},
|
||||
"type": "array"
|
||||
},
|
||||
"vpcServiceRestriction": {
|
||||
"$ref": "VpcServiceRestriction",
|
||||
"description": "Alpha. Configuration for within Perimeter allowed APIs."
|
||||
}
|
||||
},
|
||||
"type": "object"
|
||||
},
|
||||
"Status": {
|
||||
"description": "The `Status` type defines a logical error model that is suitable for\ndifferent programming environments, including REST APIs and RPC APIs. It is\nused by [gRPC](https://github.com/grpc). The error model is designed to be:\n\n- Simple to use and understand for most users\n- Flexible enough to meet unexpected needs\n\n# Overview\n\nThe `Status` message contains three pieces of data: error code, error\nmessage, and error details. The error code should be an enum value of\ngoogle.rpc.Code, but it may accept additional error codes if needed. The\nerror message should be a developer-facing English message that helps\ndevelopers *understand* and *resolve* the error. If a localized user-facing\nerror message is needed, put the localized message in the error details or\nlocalize it in the client. The optional error details may contain arbitrary\ninformation about the error. There is a predefined set of error detail types\nin the package `google.rpc` that can be used for common error conditions.\n\n# Language mapping\n\nThe `Status` message is the logical representation of the error model, but it\nis not necessarily the actual wire format. When the `Status` message is\nexposed in different client libraries and different wire protocols, it can be\nmapped differently. For example, it will likely be mapped to some exceptions\nin Java, but more likely mapped to some error codes in C.\n\n# Other uses\n\nThe error model and the `Status` message can be used in a variety of\nenvironments, either with or without APIs, to provide a\nconsistent developer experience across different environments.\n\nExample uses of this error model include:\n\n- Partial errors. If a service needs to return partial errors to the client,\n it may embed the `Status` in the normal response to indicate the partial\n errors.\n\n- Workflow errors. A typical workflow has multiple steps. Each step may\n have a `Status` message for error reporting.\n\n- Batch operations. If a client uses batch request and batch response, the\n `Status` message should be used directly inside batch response, one for\n each error sub-response.\n\n- Asynchronous operations. If an API call embeds asynchronous operation\n results in its response, the status of those operations should be\n represented directly using the `Status` message.\n\n- Logging. If some API errors are stored in logs, the message `Status` could\n be used directly after any stripping needed for security/privacy reasons.",
|
||||
"description": "The `Status` type defines a logical error model that is suitable for\ndifferent programming environments, including REST APIs and RPC APIs. It is\nused by [gRPC](https://github.com/grpc). Each `Status` message contains\nthree pieces of data: error code, error message, and error details.\n\nYou can find out more about this error model and how to work with it in the\n[API Design Guide](https://cloud.google.com/apis/design/errors).",
|
||||
"id": "Status",
|
||||
"properties": {
|
||||
"code": {
|
||||
@@ -1024,6 +1072,24 @@
|
||||
}
|
||||
},
|
||||
"type": "object"
|
||||
},
|
||||
"VpcServiceRestriction": {
|
||||
"description": "Alpha. Specifies how APIs are allowed to communicate within the Service\nPerimeter.",
|
||||
"id": "VpcServiceRestriction",
|
||||
"properties": {
|
||||
"allowedServices": {
|
||||
"description": "The list of APIs usable within the Service Perimeter. Must be empty\nunless 'enable_restriction' is True.",
|
||||
"items": {
|
||||
"type": "string"
|
||||
},
|
||||
"type": "array"
|
||||
},
|
||||
"enableRestriction": {
|
||||
"description": "Whether to restrict API calls within the Service Perimeter to the list of\nAPIs specified in 'allowed_services'.",
|
||||
"type": "boolean"
|
||||
}
|
||||
},
|
||||
"type": "object"
|
||||
}
|
||||
},
|
||||
"servicePath": "",
|
||||
|
||||
Reference in New Issue
Block a user