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
@@ -196,7 +196,7 @@
|
||||
}
|
||||
}
|
||||
},
|
||||
"revision": "20190323",
|
||||
"revision": "20190622",
|
||||
"rootUrl": "https://servicecontrol.googleapis.com/",
|
||||
"schemas": {
|
||||
"AllocateInfo": {
|
||||
@@ -607,6 +607,10 @@
|
||||
"serviceConfigId": {
|
||||
"description": "The actual config id used to process the request.",
|
||||
"type": "string"
|
||||
},
|
||||
"serviceRolloutId": {
|
||||
"description": "Unimplemented. The current service rollout id used to process the request.",
|
||||
"type": "string"
|
||||
}
|
||||
},
|
||||
"type": "object"
|
||||
@@ -626,17 +630,20 @@
|
||||
"type": "string"
|
||||
},
|
||||
"type": {
|
||||
"description": "The type of the consumer which should have been defined in\n[Google Resource Manager](https://cloud.google.com/resource-manager/).",
|
||||
"enum": [
|
||||
"CONSUMER_TYPE_UNSPECIFIED",
|
||||
"PROJECT",
|
||||
"FOLDER",
|
||||
"ORGANIZATION"
|
||||
"ORGANIZATION",
|
||||
"SERVICE_SPECIFIC"
|
||||
],
|
||||
"enumDescriptions": [
|
||||
"",
|
||||
"",
|
||||
"",
|
||||
""
|
||||
"This is never used.",
|
||||
"The consumer is a Google Cloud Project.",
|
||||
"The consumer is a Google Cloud Folder.",
|
||||
"The consumer is a Google Cloud Organization.",
|
||||
"Service-specific resource container which is defined by the service\nproducer to offer their users the ability to manage service control\nfunctionalities at a finer level of granularity than the PROJECT."
|
||||
],
|
||||
"type": "string"
|
||||
}
|
||||
@@ -660,6 +667,13 @@
|
||||
"format": "int64",
|
||||
"type": "string"
|
||||
},
|
||||
"exemplars": {
|
||||
"description": "Example points. Must be in increasing order of `value` field.",
|
||||
"items": {
|
||||
"$ref": "Exemplar"
|
||||
},
|
||||
"type": "array"
|
||||
},
|
||||
"explicitBuckets": {
|
||||
"$ref": "ExplicitBuckets",
|
||||
"description": "Buckets with arbitrary user-provided width."
|
||||
@@ -695,6 +709,34 @@
|
||||
},
|
||||
"type": "object"
|
||||
},
|
||||
"Exemplar": {
|
||||
"description": "Exemplars are example points that may be used to annotate aggregated\ndistribution values. They are metadata that gives information about a\nparticular value added to a Distribution bucket, such as a trace ID that\nwas active when a value was added. They may contain further information,\nsuch as a example values and timestamps, origin, etc.",
|
||||
"id": "Exemplar",
|
||||
"properties": {
|
||||
"attachments": {
|
||||
"description": "Contextual information about the example value. Examples are:\n\n Trace: type.googleapis.com/google.monitoring.v3.SpanContext\n\n Literal string: type.googleapis.com/google.protobuf.StringValue\n\n Labels dropped during aggregation:\n type.googleapis.com/google.monitoring.v3.DroppedLabels\n\nThere may be only a single attachment of any given message type in a\nsingle exemplar, and this is enforced by the system.",
|
||||
"items": {
|
||||
"additionalProperties": {
|
||||
"description": "Properties of the object. Contains field @type with type URL.",
|
||||
"type": "any"
|
||||
},
|
||||
"type": "object"
|
||||
},
|
||||
"type": "array"
|
||||
},
|
||||
"timestamp": {
|
||||
"description": "The observation (sampling) time of the above value.",
|
||||
"format": "google-datetime",
|
||||
"type": "string"
|
||||
},
|
||||
"value": {
|
||||
"description": "Value of the exemplar point. This value determines to which bucket the\nexemplar belongs.",
|
||||
"format": "double",
|
||||
"type": "number"
|
||||
}
|
||||
},
|
||||
"type": "object"
|
||||
},
|
||||
"ExplicitBuckets": {
|
||||
"description": "Describing buckets with arbitrary user-provided width.",
|
||||
"id": "ExplicitBuckets",
|
||||
@@ -1384,6 +1426,10 @@
|
||||
"serviceConfigId": {
|
||||
"description": "The actual config id used to process the request.",
|
||||
"type": "string"
|
||||
},
|
||||
"serviceRolloutId": {
|
||||
"description": "Unimplemented. The current service rollout id used to process the request.",
|
||||
"type": "string"
|
||||
}
|
||||
},
|
||||
"type": "object"
|
||||
@@ -1561,7 +1607,7 @@
|
||||
"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": {
|
||||
|
||||
Reference in New Issue
Block a user