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
@@ -21,7 +21,7 @@
|
||||
"baseUrl": "https://monitoring.googleapis.com/",
|
||||
"batchPath": "batch",
|
||||
"canonicalName": "Monitoring",
|
||||
"description": "Manages your Stackdriver Monitoring data and configurations. Most projects must be associated with a Stackdriver account, with a few exceptions as noted on the individual method pages.",
|
||||
"description": "Manages your Stackdriver Monitoring data and configurations. Most projects must be associated with a Stackdriver account, with a few exceptions as noted on the individual method pages. The table entries below are presented in alphabetical order, not in order of common use. For explanations of the concepts found in the table entries, read the Stackdriver Monitoring documentation.",
|
||||
"discoveryVersion": "v1",
|
||||
"documentationLink": "https://cloud.google.com/monitoring/api/",
|
||||
"fullyEncodeReservedExpansion": true,
|
||||
@@ -1201,7 +1201,7 @@
|
||||
"type": "string"
|
||||
},
|
||||
"filter": {
|
||||
"description": "A monitoring filter that specifies which time series should be returned. The filter must specify a single metric type, and can additionally specify metric labels and other information. For example:\nmetric.type = \"compute.googleapis.com/instance/cpu/usage_time\" AND\n metric.label.instance_name = \"my-instance-name\"\n",
|
||||
"description": "A monitoring filter that specifies which time series should be returned. The filter must specify a single metric type, and can additionally specify metric labels and other information. For example:\nmetric.type = \"compute.googleapis.com/instance/cpu/usage_time\" AND\n metric.labels.instance_name = \"my-instance-name\"\n",
|
||||
"location": "query",
|
||||
"type": "string"
|
||||
},
|
||||
@@ -1457,7 +1457,7 @@
|
||||
}
|
||||
}
|
||||
},
|
||||
"revision": "20190331",
|
||||
"revision": "20190629",
|
||||
"rootUrl": "https://monitoring.googleapis.com/",
|
||||
"schemas": {
|
||||
"Aggregation": {
|
||||
@@ -2560,6 +2560,26 @@
|
||||
},
|
||||
"type": "array"
|
||||
},
|
||||
"launchStage": {
|
||||
"description": "Optional. The launch stage of the metric definition.",
|
||||
"enum": [
|
||||
"LAUNCH_STAGE_UNSPECIFIED",
|
||||
"EARLY_ACCESS",
|
||||
"ALPHA",
|
||||
"BETA",
|
||||
"GA",
|
||||
"DEPRECATED"
|
||||
],
|
||||
"enumDescriptions": [
|
||||
"Do not use this default value.",
|
||||
"Early Access features are limited to a closed group of testers. To use these features, you must sign up in advance and sign a Trusted Tester agreement (which includes confidentiality provisions). These features may be unstable, changed in backward-incompatible ways, and are not guaranteed to be released.",
|
||||
"Alpha is a limited availability test for releases before they are cleared for widespread use. By Alpha, all significant design issues are resolved and we are in the process of verifying functionality. Alpha customers need to apply for access, agree to applicable terms, and have their projects whitelisted. Alpha releases don\u2019t have to be feature complete, no SLAs are provided, and there are no technical support obligations, but they will be far enough along that customers can actually use them in test environments or for limited-use tests -- just like they would in normal production cases.",
|
||||
"Beta is the point at which we are ready to open a release for any customer to use. There are no SLA or technical support obligations in a Beta release. Products will be complete from a feature perspective, but may have some open outstanding issues. Beta releases are suitable for limited production use cases.",
|
||||
"GA features are open to all developers and are considered stable and fully qualified for production use.",
|
||||
"Deprecated features are scheduled to be shut down and removed. For more information, see the \u201cDeprecation Policy\u201d section of our Terms of Service (https://cloud.google.com/terms/) and the Google Cloud Platform Subject to the Deprecation Policy (https://cloud.google.com/terms/deprecation) documentation."
|
||||
],
|
||||
"type": "string"
|
||||
},
|
||||
"metadata": {
|
||||
"$ref": "MetricDescriptorMetadata",
|
||||
"description": "Optional. Metadata which can be used to guide usage of the metric."
|
||||
@@ -2627,7 +2647,7 @@
|
||||
"type": "string"
|
||||
},
|
||||
"launchStage": {
|
||||
"description": "The launch stage of the metric definition.",
|
||||
"description": "Deprecated. Please use the MetricDescriptor.launch_stage instead. The launch stage of the metric definition.",
|
||||
"enum": [
|
||||
"LAUNCH_STAGE_UNSPECIFIED",
|
||||
"EARLY_ACCESS",
|
||||
@@ -2756,6 +2776,26 @@
|
||||
},
|
||||
"type": "array"
|
||||
},
|
||||
"launchStage": {
|
||||
"description": "Optional. The launch stage of the monitored resource definition.",
|
||||
"enum": [
|
||||
"LAUNCH_STAGE_UNSPECIFIED",
|
||||
"EARLY_ACCESS",
|
||||
"ALPHA",
|
||||
"BETA",
|
||||
"GA",
|
||||
"DEPRECATED"
|
||||
],
|
||||
"enumDescriptions": [
|
||||
"Do not use this default value.",
|
||||
"Early Access features are limited to a closed group of testers. To use these features, you must sign up in advance and sign a Trusted Tester agreement (which includes confidentiality provisions). These features may be unstable, changed in backward-incompatible ways, and are not guaranteed to be released.",
|
||||
"Alpha is a limited availability test for releases before they are cleared for widespread use. By Alpha, all significant design issues are resolved and we are in the process of verifying functionality. Alpha customers need to apply for access, agree to applicable terms, and have their projects whitelisted. Alpha releases don\u2019t have to be feature complete, no SLAs are provided, and there are no technical support obligations, but they will be far enough along that customers can actually use them in test environments or for limited-use tests -- just like they would in normal production cases.",
|
||||
"Beta is the point at which we are ready to open a release for any customer to use. There are no SLA or technical support obligations in a Beta release. Products will be complete from a feature perspective, but may have some open outstanding issues. Beta releases are suitable for limited production use cases.",
|
||||
"GA features are open to all developers and are considered stable and fully qualified for production use.",
|
||||
"Deprecated features are scheduled to be shut down and removed. For more information, see the \u201cDeprecation Policy\u201d section of our Terms of Service (https://cloud.google.com/terms/) and the Google Cloud Platform Subject to the Deprecation Policy (https://cloud.google.com/terms/deprecation) documentation."
|
||||
],
|
||||
"type": "string"
|
||||
},
|
||||
"name": {
|
||||
"description": "Optional. The resource name of the monitored resource descriptor: \"projects/{project_id}/monitoredResourceDescriptors/{type}\" where {type} is the value of the type field in this object and {project_id} is a project ID that provides API-specific context for accessing the type. APIs that do not use project information can use the resource name format \"monitoredResourceDescriptors/{type}\".",
|
||||
"type": "string"
|
||||
@@ -3012,7 +3052,7 @@
|
||||
"type": "object"
|
||||
},
|
||||
"Status": {
|
||||
"description": "The Status type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC (https://github.com/grpc). The error model is designed to be:\nSimple to use and understand for most users\nFlexible enough to meet unexpected needsOverviewThe Status message contains three pieces of data: error code, error message, and error details. The error code should be an enum value of google.rpc.Code, but it may accept additional error codes if needed. The error message should be a developer-facing English message that helps developers understand and resolve the error. If a localized user-facing error message is needed, put the localized message in the error details or localize it in the client. The optional error details may contain arbitrary information about the error. There is a predefined set of error detail types in the package google.rpc that can be used for common error conditions.Language mappingThe Status message is the logical representation of the error model, but it is not necessarily the actual wire format. When the Status message is exposed in different client libraries and different wire protocols, it can be mapped differently. For example, it will likely be mapped to some exceptions in Java, but more likely mapped to some error codes in C.Other usesThe error model and the Status message can be used in a variety of environments, either with or without APIs, to provide a consistent developer experience across different environments.Example uses of this error model include:\nPartial errors. If a service needs to return partial errors to the client, it may embed the Status in the normal response to indicate the partial errors.\nWorkflow errors. A typical workflow has multiple steps. Each step may have a Status message for error reporting.\nBatch operations. If a client uses batch request and batch response, the Status message should be used directly inside batch response, one for each error sub-response.\nAsynchronous operations. If an API call embeds asynchronous operation results in its response, the status of those operations should be represented directly using the Status message.\nLogging. If some API errors are stored in logs, the message Status could be used directly after any stripping needed for security/privacy reasons.",
|
||||
"description": "The Status type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC (https://github.com/grpc). Each Status message contains three pieces of data: error code, error message, and error details.You can find out more about this error model and how to work with it in the API Design Guide (https://cloud.google.com/apis/design/errors).",
|
||||
"id": "Status",
|
||||
"properties": {
|
||||
"code": {
|
||||
@@ -3051,7 +3091,7 @@
|
||||
"type": "object"
|
||||
},
|
||||
"TimeInterval": {
|
||||
"description": "A time interval extending just after a start time through an end time. The start time must not be later than the end time. The default start time is the end time, making the startTime value technically optional. Whether this is useful depends on the MetricKind. If the start and end times are the same, the interval represents a point in time. This is appropriate for GAUGE metrics, but not for DELTA and CUMULATIVE metrics, which cover a span of time.",
|
||||
"description": "A closed time interval. It extends from the start time to the end time, and includes both: [startTime, endTime]. Valid time intervals depend on the MetricKind of the metric value. In no case can the end time be earlier than the start time.\nFor a GAUGE metric, the startTime value is technically optional; if no value is specified, the start time defaults to the value of the end time, and the interval represents a single point in time. Such an interval is valid only for GAUGE metrics, which are point-in-time measurements.\nFor DELTA and CUMULATIVE metrics, the start time must be later than the end time.\nIn all cases, the start time of the next interval must be at least a microsecond after the end time of the previous interval. Because the interval is closed, if the start time of a new interval is the same as the end time of the previous interval, data written at the new start time could overwrite data written at the previous end time.",
|
||||
"id": "TimeInterval",
|
||||
"properties": {
|
||||
"endTime": {
|
||||
|
||||
Reference in New Issue
Block a user