google-api-client 0.30.0 → 0.30.1
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/CHANGELOG.md +44 -0
- data/generated/google/apis/accesscontextmanager_v1.rb +1 -1
- data/generated/google/apis/accesscontextmanager_v1/classes.rb +8 -74
- data/generated/google/apis/accesscontextmanager_v1beta.rb +1 -1
- data/generated/google/apis/accesscontextmanager_v1beta/classes.rb +8 -74
- data/generated/google/apis/adexchangebuyer2_v2beta1.rb +1 -1
- data/generated/google/apis/adexchangebuyer2_v2beta1/classes.rb +50 -0
- data/generated/google/apis/adexchangebuyer2_v2beta1/representations.rb +16 -0
- data/generated/google/apis/cloudidentity_v1.rb +1 -1
- data/generated/google/apis/cloudidentity_v1/classes.rb +8 -74
- data/generated/google/apis/cloudidentity_v1beta1.rb +1 -1
- data/generated/google/apis/cloudidentity_v1beta1/classes.rb +8 -74
- data/generated/google/apis/cloudsearch_v1.rb +1 -1
- data/generated/google/apis/cloudsearch_v1/classes.rb +11 -0
- data/generated/google/apis/cloudsearch_v1/representations.rb +1 -0
- data/generated/google/apis/commentanalyzer_v1alpha1.rb +1 -1
- data/generated/google/apis/commentanalyzer_v1alpha1/classes.rb +9 -6
- data/generated/google/apis/compute_alpha.rb +1 -1
- data/generated/google/apis/compute_alpha/classes.rb +255 -155
- data/generated/google/apis/compute_alpha/representations.rb +4 -3
- data/generated/google/apis/compute_alpha/service.rb +11 -4
- data/generated/google/apis/compute_beta.rb +1 -1
- data/generated/google/apis/compute_beta/classes.rb +2818 -235
- data/generated/google/apis/compute_beta/representations.rb +957 -0
- data/generated/google/apis/compute_beta/service.rb +2371 -475
- data/generated/google/apis/compute_v1.rb +1 -1
- data/generated/google/apis/compute_v1/classes.rb +239 -92
- data/generated/google/apis/compute_v1/representations.rb +19 -0
- data/generated/google/apis/compute_v1/service.rb +4 -2
- data/generated/google/apis/container_v1beta1.rb +1 -1
- data/generated/google/apis/container_v1beta1/classes.rb +24 -0
- data/generated/google/apis/container_v1beta1/representations.rb +3 -0
- data/generated/google/apis/containeranalysis_v1alpha1.rb +1 -1
- data/generated/google/apis/containeranalysis_v1beta1.rb +1 -1
- data/generated/google/apis/containeranalysis_v1beta1/classes.rb +1 -0
- data/generated/google/apis/content_v2.rb +1 -1
- data/generated/google/apis/content_v2/classes.rb +1 -1
- data/generated/google/apis/content_v2_1.rb +1 -1
- data/generated/google/apis/content_v2_1/classes.rb +1 -1
- data/generated/google/apis/dialogflow_v2.rb +1 -1
- data/generated/google/apis/dialogflow_v2/classes.rb +3 -4
- data/generated/google/apis/dlp_v2.rb +1 -1
- data/generated/google/apis/dlp_v2/classes.rb +44 -0
- data/generated/google/apis/dlp_v2/representations.rb +29 -0
- data/generated/google/apis/docs_v1.rb +1 -1
- data/generated/google/apis/docs_v1/classes.rb +0 -10
- data/generated/google/apis/doubleclickbidmanager_v1.rb +1 -1
- data/generated/google/apis/healthcare_v1alpha2.rb +1 -1
- data/generated/google/apis/healthcare_v1alpha2/classes.rb +7 -6
- data/generated/google/apis/healthcare_v1beta1.rb +1 -1
- data/generated/google/apis/healthcare_v1beta1/classes.rb +1 -1
- data/generated/google/apis/jobs_v2.rb +1 -1
- data/generated/google/apis/jobs_v2/classes.rb +2 -2
- data/generated/google/apis/jobs_v3.rb +1 -1
- data/generated/google/apis/jobs_v3/classes.rb +4 -3
- data/generated/google/apis/logging_v2.rb +1 -1
- data/generated/google/apis/logging_v2/classes.rb +4 -1
- data/generated/google/apis/ml_v1.rb +1 -1
- data/generated/google/apis/ml_v1/classes.rb +6 -0
- data/generated/google/apis/ml_v1/representations.rb +1 -0
- data/generated/google/apis/monitoring_v3.rb +1 -1
- data/generated/google/apis/monitoring_v3/service.rb +1 -1
- data/generated/google/apis/redis_v1.rb +1 -1
- data/generated/google/apis/redis_v1/classes.rb +125 -0
- data/generated/google/apis/redis_v1/representations.rb +83 -0
- data/generated/google/apis/redis_v1/service.rb +78 -0
- data/generated/google/apis/redis_v1beta1.rb +1 -1
- data/generated/google/apis/redis_v1beta1/classes.rb +125 -0
- data/generated/google/apis/redis_v1beta1/representations.rb +83 -0
- data/generated/google/apis/redis_v1beta1/service.rb +78 -0
- data/generated/google/apis/securitycenter_v1.rb +1 -1
- data/generated/google/apis/securitycenter_v1/classes.rb +10 -76
- data/generated/google/apis/securitycenter_v1beta1.rb +1 -1
- data/generated/google/apis/securitycenter_v1beta1/classes.rb +10 -76
- data/generated/google/apis/serviceconsumermanagement_v1.rb +1 -1
- data/generated/google/apis/serviceconsumermanagement_v1/classes.rb +8 -74
- data/generated/google/apis/servicenetworking_v1.rb +1 -1
- data/generated/google/apis/servicenetworking_v1/classes.rb +8 -74
- data/generated/google/apis/servicenetworking_v1beta.rb +1 -1
- data/generated/google/apis/servicenetworking_v1beta/classes.rb +8 -74
- data/generated/google/apis/serviceusage_v1.rb +1 -1
- data/generated/google/apis/serviceusage_v1/classes.rb +8 -74
- data/generated/google/apis/serviceusage_v1beta1.rb +1 -1
- data/generated/google/apis/serviceusage_v1beta1/classes.rb +8 -74
- data/generated/google/apis/speech_v1p1beta1.rb +1 -1
- data/generated/google/apis/speech_v1p1beta1/classes.rb +13 -0
- data/generated/google/apis/speech_v1p1beta1/representations.rb +1 -0
- data/generated/google/apis/streetviewpublish_v1.rb +1 -1
- data/generated/google/apis/streetviewpublish_v1/classes.rb +12 -111
- data/generated/google/apis/toolresults_v1beta3.rb +1 -1
- data/generated/google/apis/toolresults_v1beta3/classes.rb +8 -74
- data/generated/google/apis/vision_v1.rb +1 -1
- data/generated/google/apis/vision_v1/classes.rb +36 -20
- data/generated/google/apis/vision_v1p1beta1.rb +1 -1
- data/generated/google/apis/vision_v1p1beta1/classes.rb +36 -20
- data/generated/google/apis/vision_v1p2beta1.rb +1 -1
- data/generated/google/apis/vision_v1p2beta1/classes.rb +36 -20
- data/lib/google/apis/version.rb +1 -1
- metadata +2 -2
@@ -26,7 +26,7 @@ module Google
|
|
26
26
|
# @see https://console.cloud.google.com/apis/api/securitycenter.googleapis.com/overview
|
27
27
|
module SecuritycenterV1
|
28
28
|
VERSION = 'V1'
|
29
|
-
REVISION = '
|
29
|
+
REVISION = '20190529'
|
30
30
|
|
31
31
|
# View and manage your data across Google Cloud Platform services
|
32
32
|
AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform'
|
@@ -368,8 +368,8 @@ module Google
|
|
368
368
|
attr_accessor :create_time
|
369
369
|
|
370
370
|
# The time at which the event took place. For example, if the finding
|
371
|
-
# represents an open firewall it would capture the time the
|
372
|
-
#
|
371
|
+
# represents an open firewall it would capture the time the detector believes
|
372
|
+
# the firewall became open. The accuracy is determined by the detector.
|
373
373
|
# Corresponds to the JSON property `eventTime`
|
374
374
|
# @return [String]
|
375
375
|
attr_accessor :event_time
|
@@ -1065,43 +1065,10 @@ module Google
|
|
1065
1065
|
|
1066
1066
|
# The `Status` type defines a logical error model that is suitable for
|
1067
1067
|
# different programming environments, including REST APIs and RPC APIs. It is
|
1068
|
-
# used by [gRPC](https://github.com/grpc).
|
1069
|
-
#
|
1070
|
-
#
|
1071
|
-
#
|
1072
|
-
# The `Status` message contains three pieces of data: error code, error
|
1073
|
-
# message, and error details. The error code should be an enum value of
|
1074
|
-
# google.rpc.Code, but it may accept additional error codes if needed. The
|
1075
|
-
# error message should be a developer-facing English message that helps
|
1076
|
-
# developers *understand* and *resolve* the error. If a localized user-facing
|
1077
|
-
# error message is needed, put the localized message in the error details or
|
1078
|
-
# localize it in the client. The optional error details may contain arbitrary
|
1079
|
-
# information about the error. There is a predefined set of error detail types
|
1080
|
-
# in the package `google.rpc` that can be used for common error conditions.
|
1081
|
-
# # Language mapping
|
1082
|
-
# The `Status` message is the logical representation of the error model, but it
|
1083
|
-
# is not necessarily the actual wire format. When the `Status` message is
|
1084
|
-
# exposed in different client libraries and different wire protocols, it can be
|
1085
|
-
# mapped differently. For example, it will likely be mapped to some exceptions
|
1086
|
-
# in Java, but more likely mapped to some error codes in C.
|
1087
|
-
# # Other uses
|
1088
|
-
# The error model and the `Status` message can be used in a variety of
|
1089
|
-
# environments, either with or without APIs, to provide a
|
1090
|
-
# consistent developer experience across different environments.
|
1091
|
-
# Example uses of this error model include:
|
1092
|
-
# - Partial errors. If a service needs to return partial errors to the client,
|
1093
|
-
# it may embed the `Status` in the normal response to indicate the partial
|
1094
|
-
# errors.
|
1095
|
-
# - Workflow errors. A typical workflow has multiple steps. Each step may
|
1096
|
-
# have a `Status` message for error reporting.
|
1097
|
-
# - Batch operations. If a client uses batch request and batch response, the
|
1098
|
-
# `Status` message should be used directly inside batch response, one for
|
1099
|
-
# each error sub-response.
|
1100
|
-
# - Asynchronous operations. If an API call embeds asynchronous operation
|
1101
|
-
# results in its response, the status of those operations should be
|
1102
|
-
# represented directly using the `Status` message.
|
1103
|
-
# - Logging. If some API errors are stored in logs, the message `Status` could
|
1104
|
-
# be used directly after any stripping needed for security/privacy reasons.
|
1068
|
+
# used by [gRPC](https://github.com/grpc). Each `Status` message contains
|
1069
|
+
# three pieces of data: error code, error message, and error details.
|
1070
|
+
# You can find out more about this error model and how to work with it in the
|
1071
|
+
# [API Design Guide](https://cloud.google.com/apis/design/errors).
|
1105
1072
|
# Corresponds to the JSON property `error`
|
1106
1073
|
# @return [Google::Apis::SecuritycenterV1::Status]
|
1107
1074
|
attr_accessor :error
|
@@ -1509,43 +1476,10 @@ module Google
|
|
1509
1476
|
|
1510
1477
|
# The `Status` type defines a logical error model that is suitable for
|
1511
1478
|
# different programming environments, including REST APIs and RPC APIs. It is
|
1512
|
-
# used by [gRPC](https://github.com/grpc).
|
1513
|
-
#
|
1514
|
-
#
|
1515
|
-
#
|
1516
|
-
# The `Status` message contains three pieces of data: error code, error
|
1517
|
-
# message, and error details. The error code should be an enum value of
|
1518
|
-
# google.rpc.Code, but it may accept additional error codes if needed. The
|
1519
|
-
# error message should be a developer-facing English message that helps
|
1520
|
-
# developers *understand* and *resolve* the error. If a localized user-facing
|
1521
|
-
# error message is needed, put the localized message in the error details or
|
1522
|
-
# localize it in the client. The optional error details may contain arbitrary
|
1523
|
-
# information about the error. There is a predefined set of error detail types
|
1524
|
-
# in the package `google.rpc` that can be used for common error conditions.
|
1525
|
-
# # Language mapping
|
1526
|
-
# The `Status` message is the logical representation of the error model, but it
|
1527
|
-
# is not necessarily the actual wire format. When the `Status` message is
|
1528
|
-
# exposed in different client libraries and different wire protocols, it can be
|
1529
|
-
# mapped differently. For example, it will likely be mapped to some exceptions
|
1530
|
-
# in Java, but more likely mapped to some error codes in C.
|
1531
|
-
# # Other uses
|
1532
|
-
# The error model and the `Status` message can be used in a variety of
|
1533
|
-
# environments, either with or without APIs, to provide a
|
1534
|
-
# consistent developer experience across different environments.
|
1535
|
-
# Example uses of this error model include:
|
1536
|
-
# - Partial errors. If a service needs to return partial errors to the client,
|
1537
|
-
# it may embed the `Status` in the normal response to indicate the partial
|
1538
|
-
# errors.
|
1539
|
-
# - Workflow errors. A typical workflow has multiple steps. Each step may
|
1540
|
-
# have a `Status` message for error reporting.
|
1541
|
-
# - Batch operations. If a client uses batch request and batch response, the
|
1542
|
-
# `Status` message should be used directly inside batch response, one for
|
1543
|
-
# each error sub-response.
|
1544
|
-
# - Asynchronous operations. If an API call embeds asynchronous operation
|
1545
|
-
# results in its response, the status of those operations should be
|
1546
|
-
# represented directly using the `Status` message.
|
1547
|
-
# - Logging. If some API errors are stored in logs, the message `Status` could
|
1548
|
-
# be used directly after any stripping needed for security/privacy reasons.
|
1479
|
+
# used by [gRPC](https://github.com/grpc). Each `Status` message contains
|
1480
|
+
# three pieces of data: error code, error message, and error details.
|
1481
|
+
# You can find out more about this error model and how to work with it in the
|
1482
|
+
# [API Design Guide](https://cloud.google.com/apis/design/errors).
|
1549
1483
|
class Status
|
1550
1484
|
include Google::Apis::Core::Hashable
|
1551
1485
|
|
@@ -26,7 +26,7 @@ module Google
|
|
26
26
|
# @see https://console.cloud.google.com/apis/api/securitycenter.googleapis.com/overview
|
27
27
|
module SecuritycenterV1beta1
|
28
28
|
VERSION = 'V1beta1'
|
29
|
-
REVISION = '
|
29
|
+
REVISION = '20190529'
|
30
30
|
|
31
31
|
# View and manage your data across Google Cloud Platform services
|
32
32
|
AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform'
|
@@ -373,8 +373,8 @@ module Google
|
|
373
373
|
attr_accessor :create_time
|
374
374
|
|
375
375
|
# The time at which the event took place. For example, if the finding
|
376
|
-
# represents an open firewall it would capture the time the
|
377
|
-
#
|
376
|
+
# represents an open firewall it would capture the time the detector believes
|
377
|
+
# the firewall became open. The accuracy is determined by the detector.
|
378
378
|
# Corresponds to the JSON property `eventTime`
|
379
379
|
# @return [String]
|
380
380
|
attr_accessor :event_time
|
@@ -952,43 +952,10 @@ module Google
|
|
952
952
|
|
953
953
|
# The `Status` type defines a logical error model that is suitable for
|
954
954
|
# different programming environments, including REST APIs and RPC APIs. It is
|
955
|
-
# used by [gRPC](https://github.com/grpc).
|
956
|
-
#
|
957
|
-
#
|
958
|
-
#
|
959
|
-
# The `Status` message contains three pieces of data: error code, error
|
960
|
-
# message, and error details. The error code should be an enum value of
|
961
|
-
# google.rpc.Code, but it may accept additional error codes if needed. The
|
962
|
-
# error message should be a developer-facing English message that helps
|
963
|
-
# developers *understand* and *resolve* the error. If a localized user-facing
|
964
|
-
# error message is needed, put the localized message in the error details or
|
965
|
-
# localize it in the client. The optional error details may contain arbitrary
|
966
|
-
# information about the error. There is a predefined set of error detail types
|
967
|
-
# in the package `google.rpc` that can be used for common error conditions.
|
968
|
-
# # Language mapping
|
969
|
-
# The `Status` message is the logical representation of the error model, but it
|
970
|
-
# is not necessarily the actual wire format. When the `Status` message is
|
971
|
-
# exposed in different client libraries and different wire protocols, it can be
|
972
|
-
# mapped differently. For example, it will likely be mapped to some exceptions
|
973
|
-
# in Java, but more likely mapped to some error codes in C.
|
974
|
-
# # Other uses
|
975
|
-
# The error model and the `Status` message can be used in a variety of
|
976
|
-
# environments, either with or without APIs, to provide a
|
977
|
-
# consistent developer experience across different environments.
|
978
|
-
# Example uses of this error model include:
|
979
|
-
# - Partial errors. If a service needs to return partial errors to the client,
|
980
|
-
# it may embed the `Status` in the normal response to indicate the partial
|
981
|
-
# errors.
|
982
|
-
# - Workflow errors. A typical workflow has multiple steps. Each step may
|
983
|
-
# have a `Status` message for error reporting.
|
984
|
-
# - Batch operations. If a client uses batch request and batch response, the
|
985
|
-
# `Status` message should be used directly inside batch response, one for
|
986
|
-
# each error sub-response.
|
987
|
-
# - Asynchronous operations. If an API call embeds asynchronous operation
|
988
|
-
# results in its response, the status of those operations should be
|
989
|
-
# represented directly using the `Status` message.
|
990
|
-
# - Logging. If some API errors are stored in logs, the message `Status` could
|
991
|
-
# be used directly after any stripping needed for security/privacy reasons.
|
955
|
+
# used by [gRPC](https://github.com/grpc). Each `Status` message contains
|
956
|
+
# three pieces of data: error code, error message, and error details.
|
957
|
+
# You can find out more about this error model and how to work with it in the
|
958
|
+
# [API Design Guide](https://cloud.google.com/apis/design/errors).
|
992
959
|
# Corresponds to the JSON property `error`
|
993
960
|
# @return [Google::Apis::SecuritycenterV1beta1::Status]
|
994
961
|
attr_accessor :error
|
@@ -1396,43 +1363,10 @@ module Google
|
|
1396
1363
|
|
1397
1364
|
# The `Status` type defines a logical error model that is suitable for
|
1398
1365
|
# different programming environments, including REST APIs and RPC APIs. It is
|
1399
|
-
# used by [gRPC](https://github.com/grpc).
|
1400
|
-
#
|
1401
|
-
#
|
1402
|
-
#
|
1403
|
-
# The `Status` message contains three pieces of data: error code, error
|
1404
|
-
# message, and error details. The error code should be an enum value of
|
1405
|
-
# google.rpc.Code, but it may accept additional error codes if needed. The
|
1406
|
-
# error message should be a developer-facing English message that helps
|
1407
|
-
# developers *understand* and *resolve* the error. If a localized user-facing
|
1408
|
-
# error message is needed, put the localized message in the error details or
|
1409
|
-
# localize it in the client. The optional error details may contain arbitrary
|
1410
|
-
# information about the error. There is a predefined set of error detail types
|
1411
|
-
# in the package `google.rpc` that can be used for common error conditions.
|
1412
|
-
# # Language mapping
|
1413
|
-
# The `Status` message is the logical representation of the error model, but it
|
1414
|
-
# is not necessarily the actual wire format. When the `Status` message is
|
1415
|
-
# exposed in different client libraries and different wire protocols, it can be
|
1416
|
-
# mapped differently. For example, it will likely be mapped to some exceptions
|
1417
|
-
# in Java, but more likely mapped to some error codes in C.
|
1418
|
-
# # Other uses
|
1419
|
-
# The error model and the `Status` message can be used in a variety of
|
1420
|
-
# environments, either with or without APIs, to provide a
|
1421
|
-
# consistent developer experience across different environments.
|
1422
|
-
# Example uses of this error model include:
|
1423
|
-
# - Partial errors. If a service needs to return partial errors to the client,
|
1424
|
-
# it may embed the `Status` in the normal response to indicate the partial
|
1425
|
-
# errors.
|
1426
|
-
# - Workflow errors. A typical workflow has multiple steps. Each step may
|
1427
|
-
# have a `Status` message for error reporting.
|
1428
|
-
# - Batch operations. If a client uses batch request and batch response, the
|
1429
|
-
# `Status` message should be used directly inside batch response, one for
|
1430
|
-
# each error sub-response.
|
1431
|
-
# - Asynchronous operations. If an API call embeds asynchronous operation
|
1432
|
-
# results in its response, the status of those operations should be
|
1433
|
-
# represented directly using the `Status` message.
|
1434
|
-
# - Logging. If some API errors are stored in logs, the message `Status` could
|
1435
|
-
# be used directly after any stripping needed for security/privacy reasons.
|
1366
|
+
# used by [gRPC](https://github.com/grpc). Each `Status` message contains
|
1367
|
+
# three pieces of data: error code, error message, and error details.
|
1368
|
+
# You can find out more about this error model and how to work with it in the
|
1369
|
+
# [API Design Guide](https://cloud.google.com/apis/design/errors).
|
1436
1370
|
class Status
|
1437
1371
|
include Google::Apis::Core::Hashable
|
1438
1372
|
|
@@ -25,7 +25,7 @@ module Google
|
|
25
25
|
# @see https://cloud.google.com/service-consumer-management/docs/overview
|
26
26
|
module ServiceconsumermanagementV1
|
27
27
|
VERSION = 'V1'
|
28
|
-
REVISION = '
|
28
|
+
REVISION = '20190530'
|
29
29
|
|
30
30
|
# View and manage your data across Google Cloud Platform services
|
31
31
|
AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform'
|
@@ -2347,43 +2347,10 @@ module Google
|
|
2347
2347
|
|
2348
2348
|
# The `Status` type defines a logical error model that is suitable for
|
2349
2349
|
# different programming environments, including REST APIs and RPC APIs. It is
|
2350
|
-
# used by [gRPC](https://github.com/grpc).
|
2351
|
-
#
|
2352
|
-
#
|
2353
|
-
#
|
2354
|
-
# The `Status` message contains three pieces of data: error code, error
|
2355
|
-
# message, and error details. The error code should be an enum value of
|
2356
|
-
# google.rpc.Code, but it may accept additional error codes if needed. The
|
2357
|
-
# error message should be a developer-facing English message that helps
|
2358
|
-
# developers *understand* and *resolve* the error. If a localized user-facing
|
2359
|
-
# error message is needed, put the localized message in the error details or
|
2360
|
-
# localize it in the client. The optional error details may contain arbitrary
|
2361
|
-
# information about the error. There is a predefined set of error detail types
|
2362
|
-
# in the package `google.rpc` that can be used for common error conditions.
|
2363
|
-
# # Language mapping
|
2364
|
-
# The `Status` message is the logical representation of the error model, but it
|
2365
|
-
# is not necessarily the actual wire format. When the `Status` message is
|
2366
|
-
# exposed in different client libraries and different wire protocols, it can be
|
2367
|
-
# mapped differently. For example, it will likely be mapped to some exceptions
|
2368
|
-
# in Java, but more likely mapped to some error codes in C.
|
2369
|
-
# # Other uses
|
2370
|
-
# The error model and the `Status` message can be used in a variety of
|
2371
|
-
# environments, either with or without APIs, to provide a
|
2372
|
-
# consistent developer experience across different environments.
|
2373
|
-
# Example uses of this error model include:
|
2374
|
-
# - Partial errors. If a service needs to return partial errors to the client,
|
2375
|
-
# it may embed the `Status` in the normal response to indicate the partial
|
2376
|
-
# errors.
|
2377
|
-
# - Workflow errors. A typical workflow has multiple steps. Each step may
|
2378
|
-
# have a `Status` message for error reporting.
|
2379
|
-
# - Batch operations. If a client uses batch request and batch response, the
|
2380
|
-
# `Status` message should be used directly inside batch response, one for
|
2381
|
-
# each error sub-response.
|
2382
|
-
# - Asynchronous operations. If an API call embeds asynchronous operation
|
2383
|
-
# results in its response, the status of those operations should be
|
2384
|
-
# represented directly using the `Status` message.
|
2385
|
-
# - Logging. If some API errors are stored in logs, the message `Status` could
|
2386
|
-
# be used directly after any stripping needed for security/privacy reasons.
|
2350
|
+
# used by [gRPC](https://github.com/grpc). Each `Status` message contains
|
2351
|
+
# three pieces of data: error code, error message, and error details.
|
2352
|
+
# You can find out more about this error model and how to work with it in the
|
2353
|
+
# [API Design Guide](https://cloud.google.com/apis/design/errors).
|
2387
2354
|
# Corresponds to the JSON property `error`
|
2388
2355
|
# @return [Google::Apis::ServiceconsumermanagementV1::Status]
|
2389
2356
|
attr_accessor :error
|
@@ -3277,43 +3244,10 @@ module Google
|
|
3277
3244
|
|
3278
3245
|
# The `Status` type defines a logical error model that is suitable for
|
3279
3246
|
# different programming environments, including REST APIs and RPC APIs. It is
|
3280
|
-
# used by [gRPC](https://github.com/grpc).
|
3281
|
-
#
|
3282
|
-
#
|
3283
|
-
#
|
3284
|
-
# The `Status` message contains three pieces of data: error code, error
|
3285
|
-
# message, and error details. The error code should be an enum value of
|
3286
|
-
# google.rpc.Code, but it may accept additional error codes if needed. The
|
3287
|
-
# error message should be a developer-facing English message that helps
|
3288
|
-
# developers *understand* and *resolve* the error. If a localized user-facing
|
3289
|
-
# error message is needed, put the localized message in the error details or
|
3290
|
-
# localize it in the client. The optional error details may contain arbitrary
|
3291
|
-
# information about the error. There is a predefined set of error detail types
|
3292
|
-
# in the package `google.rpc` that can be used for common error conditions.
|
3293
|
-
# # Language mapping
|
3294
|
-
# The `Status` message is the logical representation of the error model, but it
|
3295
|
-
# is not necessarily the actual wire format. When the `Status` message is
|
3296
|
-
# exposed in different client libraries and different wire protocols, it can be
|
3297
|
-
# mapped differently. For example, it will likely be mapped to some exceptions
|
3298
|
-
# in Java, but more likely mapped to some error codes in C.
|
3299
|
-
# # Other uses
|
3300
|
-
# The error model and the `Status` message can be used in a variety of
|
3301
|
-
# environments, either with or without APIs, to provide a
|
3302
|
-
# consistent developer experience across different environments.
|
3303
|
-
# Example uses of this error model include:
|
3304
|
-
# - Partial errors. If a service needs to return partial errors to the client,
|
3305
|
-
# it may embed the `Status` in the normal response to indicate the partial
|
3306
|
-
# errors.
|
3307
|
-
# - Workflow errors. A typical workflow has multiple steps. Each step may
|
3308
|
-
# have a `Status` message for error reporting.
|
3309
|
-
# - Batch operations. If a client uses batch request and batch response, the
|
3310
|
-
# `Status` message should be used directly inside batch response, one for
|
3311
|
-
# each error sub-response.
|
3312
|
-
# - Asynchronous operations. If an API call embeds asynchronous operation
|
3313
|
-
# results in its response, the status of those operations should be
|
3314
|
-
# represented directly using the `Status` message.
|
3315
|
-
# - Logging. If some API errors are stored in logs, the message `Status` could
|
3316
|
-
# be used directly after any stripping needed for security/privacy reasons.
|
3247
|
+
# used by [gRPC](https://github.com/grpc). Each `Status` message contains
|
3248
|
+
# three pieces of data: error code, error message, and error details.
|
3249
|
+
# You can find out more about this error model and how to work with it in the
|
3250
|
+
# [API Design Guide](https://cloud.google.com/apis/design/errors).
|
3317
3251
|
class Status
|
3318
3252
|
include Google::Apis::Core::Hashable
|
3319
3253
|
|
@@ -26,7 +26,7 @@ module Google
|
|
26
26
|
# @see https://cloud.google.com/service-infrastructure/docs/service-networking/getting-started
|
27
27
|
module ServicenetworkingV1
|
28
28
|
VERSION = 'V1'
|
29
|
-
REVISION = '
|
29
|
+
REVISION = '20190530'
|
30
30
|
|
31
31
|
# View and manage your data across Google Cloud Platform services
|
32
32
|
AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform'
|
@@ -2362,43 +2362,10 @@ module Google
|
|
2362
2362
|
|
2363
2363
|
# The `Status` type defines a logical error model that is suitable for
|
2364
2364
|
# different programming environments, including REST APIs and RPC APIs. It is
|
2365
|
-
# used by [gRPC](https://github.com/grpc).
|
2366
|
-
#
|
2367
|
-
#
|
2368
|
-
#
|
2369
|
-
# The `Status` message contains three pieces of data: error code, error
|
2370
|
-
# message, and error details. The error code should be an enum value of
|
2371
|
-
# google.rpc.Code, but it may accept additional error codes if needed. The
|
2372
|
-
# error message should be a developer-facing English message that helps
|
2373
|
-
# developers *understand* and *resolve* the error. If a localized user-facing
|
2374
|
-
# error message is needed, put the localized message in the error details or
|
2375
|
-
# localize it in the client. The optional error details may contain arbitrary
|
2376
|
-
# information about the error. There is a predefined set of error detail types
|
2377
|
-
# in the package `google.rpc` that can be used for common error conditions.
|
2378
|
-
# # Language mapping
|
2379
|
-
# The `Status` message is the logical representation of the error model, but it
|
2380
|
-
# is not necessarily the actual wire format. When the `Status` message is
|
2381
|
-
# exposed in different client libraries and different wire protocols, it can be
|
2382
|
-
# mapped differently. For example, it will likely be mapped to some exceptions
|
2383
|
-
# in Java, but more likely mapped to some error codes in C.
|
2384
|
-
# # Other uses
|
2385
|
-
# The error model and the `Status` message can be used in a variety of
|
2386
|
-
# environments, either with or without APIs, to provide a
|
2387
|
-
# consistent developer experience across different environments.
|
2388
|
-
# Example uses of this error model include:
|
2389
|
-
# - Partial errors. If a service needs to return partial errors to the client,
|
2390
|
-
# it may embed the `Status` in the normal response to indicate the partial
|
2391
|
-
# errors.
|
2392
|
-
# - Workflow errors. A typical workflow has multiple steps. Each step may
|
2393
|
-
# have a `Status` message for error reporting.
|
2394
|
-
# - Batch operations. If a client uses batch request and batch response, the
|
2395
|
-
# `Status` message should be used directly inside batch response, one for
|
2396
|
-
# each error sub-response.
|
2397
|
-
# - Asynchronous operations. If an API call embeds asynchronous operation
|
2398
|
-
# results in its response, the status of those operations should be
|
2399
|
-
# represented directly using the `Status` message.
|
2400
|
-
# - Logging. If some API errors are stored in logs, the message `Status` could
|
2401
|
-
# be used directly after any stripping needed for security/privacy reasons.
|
2365
|
+
# used by [gRPC](https://github.com/grpc). Each `Status` message contains
|
2366
|
+
# three pieces of data: error code, error message, and error details.
|
2367
|
+
# You can find out more about this error model and how to work with it in the
|
2368
|
+
# [API Design Guide](https://cloud.google.com/apis/design/errors).
|
2402
2369
|
# Corresponds to the JSON property `error`
|
2403
2370
|
# @return [Google::Apis::ServicenetworkingV1::Status]
|
2404
2371
|
attr_accessor :error
|
@@ -3252,43 +3219,10 @@ module Google
|
|
3252
3219
|
|
3253
3220
|
# The `Status` type defines a logical error model that is suitable for
|
3254
3221
|
# different programming environments, including REST APIs and RPC APIs. It is
|
3255
|
-
# used by [gRPC](https://github.com/grpc).
|
3256
|
-
#
|
3257
|
-
#
|
3258
|
-
#
|
3259
|
-
# The `Status` message contains three pieces of data: error code, error
|
3260
|
-
# message, and error details. The error code should be an enum value of
|
3261
|
-
# google.rpc.Code, but it may accept additional error codes if needed. The
|
3262
|
-
# error message should be a developer-facing English message that helps
|
3263
|
-
# developers *understand* and *resolve* the error. If a localized user-facing
|
3264
|
-
# error message is needed, put the localized message in the error details or
|
3265
|
-
# localize it in the client. The optional error details may contain arbitrary
|
3266
|
-
# information about the error. There is a predefined set of error detail types
|
3267
|
-
# in the package `google.rpc` that can be used for common error conditions.
|
3268
|
-
# # Language mapping
|
3269
|
-
# The `Status` message is the logical representation of the error model, but it
|
3270
|
-
# is not necessarily the actual wire format. When the `Status` message is
|
3271
|
-
# exposed in different client libraries and different wire protocols, it can be
|
3272
|
-
# mapped differently. For example, it will likely be mapped to some exceptions
|
3273
|
-
# in Java, but more likely mapped to some error codes in C.
|
3274
|
-
# # Other uses
|
3275
|
-
# The error model and the `Status` message can be used in a variety of
|
3276
|
-
# environments, either with or without APIs, to provide a
|
3277
|
-
# consistent developer experience across different environments.
|
3278
|
-
# Example uses of this error model include:
|
3279
|
-
# - Partial errors. If a service needs to return partial errors to the client,
|
3280
|
-
# it may embed the `Status` in the normal response to indicate the partial
|
3281
|
-
# errors.
|
3282
|
-
# - Workflow errors. A typical workflow has multiple steps. Each step may
|
3283
|
-
# have a `Status` message for error reporting.
|
3284
|
-
# - Batch operations. If a client uses batch request and batch response, the
|
3285
|
-
# `Status` message should be used directly inside batch response, one for
|
3286
|
-
# each error sub-response.
|
3287
|
-
# - Asynchronous operations. If an API call embeds asynchronous operation
|
3288
|
-
# results in its response, the status of those operations should be
|
3289
|
-
# represented directly using the `Status` message.
|
3290
|
-
# - Logging. If some API errors are stored in logs, the message `Status` could
|
3291
|
-
# be used directly after any stripping needed for security/privacy reasons.
|
3222
|
+
# used by [gRPC](https://github.com/grpc). Each `Status` message contains
|
3223
|
+
# three pieces of data: error code, error message, and error details.
|
3224
|
+
# You can find out more about this error model and how to work with it in the
|
3225
|
+
# [API Design Guide](https://cloud.google.com/apis/design/errors).
|
3292
3226
|
class Status
|
3293
3227
|
include Google::Apis::Core::Hashable
|
3294
3228
|
|
@@ -26,7 +26,7 @@ module Google
|
|
26
26
|
# @see https://cloud.google.com/service-infrastructure/docs/service-networking/getting-started
|
27
27
|
module ServicenetworkingV1beta
|
28
28
|
VERSION = 'V1beta'
|
29
|
-
REVISION = '
|
29
|
+
REVISION = '20190530'
|
30
30
|
|
31
31
|
# View and manage your data across Google Cloud Platform services
|
32
32
|
AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform'
|