google-cloud-tasks 0.5.0 → 0.6.0
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/README.md +1 -1
- data/lib/google/cloud/tasks/v2/cloud_tasks_client.rb +1254 -0
- data/lib/google/cloud/tasks/v2/cloud_tasks_client_config.json +106 -0
- data/lib/google/cloud/tasks/v2/cloudtasks_pb.rb +99 -0
- data/lib/google/cloud/tasks/v2/cloudtasks_services_pb.rb +200 -0
- data/lib/google/cloud/tasks/v2/credentials.rb +41 -0
- data/lib/google/cloud/tasks/v2/doc/google/cloud/tasks/v2/cloudtasks.rb +340 -0
- data/lib/google/cloud/tasks/v2/doc/google/cloud/tasks/v2/queue.rb +333 -0
- data/lib/google/cloud/tasks/v2/doc/google/cloud/tasks/v2/target.rb +270 -0
- data/lib/google/cloud/tasks/v2/doc/google/cloud/tasks/v2/task.rb +170 -0
- data/lib/google/cloud/tasks/v2/doc/google/iam/v1/iam_policy.rb +63 -0
- data/lib/google/cloud/tasks/v2/doc/google/iam/v1/policy.rb +104 -0
- data/lib/google/cloud/tasks/v2/doc/google/protobuf/any.rb +130 -0
- data/lib/google/cloud/tasks/v2/doc/google/protobuf/duration.rb +91 -0
- data/lib/google/cloud/tasks/v2/doc/google/protobuf/empty.rb +29 -0
- data/lib/google/cloud/tasks/v2/doc/google/protobuf/field_mask.rb +230 -0
- data/lib/google/cloud/tasks/v2/doc/google/protobuf/timestamp.rb +109 -0
- data/lib/google/cloud/tasks/v2/doc/google/rpc/status.rb +87 -0
- data/lib/google/cloud/tasks/v2/helpers.rb +56 -0
- data/lib/google/cloud/tasks/v2/queue_pb.rb +51 -0
- data/lib/google/cloud/tasks/v2/target_pb.rb +44 -0
- data/lib/google/cloud/tasks/v2/task_pb.rb +50 -0
- data/lib/google/cloud/tasks/v2.rb +139 -0
- data/lib/google/cloud/tasks.rb +2 -2
- metadata +24 -2
@@ -0,0 +1,104 @@
|
|
1
|
+
# Copyright 2019 Google LLC
|
2
|
+
#
|
3
|
+
# Licensed under the Apache License, Version 2.0 (the "License");
|
4
|
+
# you may not use this file except in compliance with the License.
|
5
|
+
# You may obtain a copy of the License at
|
6
|
+
#
|
7
|
+
# https://www.apache.org/licenses/LICENSE-2.0
|
8
|
+
#
|
9
|
+
# Unless required by applicable law or agreed to in writing, software
|
10
|
+
# distributed under the License is distributed on an "AS IS" BASIS,
|
11
|
+
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
12
|
+
# See the License for the specific language governing permissions and
|
13
|
+
# limitations under the License.
|
14
|
+
|
15
|
+
|
16
|
+
module Google
|
17
|
+
module Iam
|
18
|
+
module V1
|
19
|
+
# Defines an Identity and Access Management (IAM) policy. It is used to
|
20
|
+
# specify access control policies for Cloud Platform resources.
|
21
|
+
#
|
22
|
+
#
|
23
|
+
# A `Policy` consists of a list of `bindings`. A `Binding` binds a list of
|
24
|
+
# `members` to a `role`, where the members can be user accounts, Google groups,
|
25
|
+
# Google domains, and service accounts. A `role` is a named list of permissions
|
26
|
+
# defined by IAM.
|
27
|
+
#
|
28
|
+
# **Example**
|
29
|
+
#
|
30
|
+
# {
|
31
|
+
# "bindings": [
|
32
|
+
# {
|
33
|
+
# "role": "roles/owner",
|
34
|
+
# "members": [
|
35
|
+
# "user:mike@example.com",
|
36
|
+
# "group:admins@example.com",
|
37
|
+
# "domain:google.com",
|
38
|
+
# "serviceAccount:my-other-app@appspot.gserviceaccount.com",
|
39
|
+
# ]
|
40
|
+
# },
|
41
|
+
# {
|
42
|
+
# "role": "roles/viewer",
|
43
|
+
# "members": ["user:sean@example.com"]
|
44
|
+
# }
|
45
|
+
# ]
|
46
|
+
# }
|
47
|
+
#
|
48
|
+
# For a description of IAM and its features, see the
|
49
|
+
# [IAM developer's guide](https://cloud.google.com/iam).
|
50
|
+
# @!attribute [rw] version
|
51
|
+
# @return [Integer]
|
52
|
+
# Version of the `Policy`. The default version is 0.
|
53
|
+
# @!attribute [rw] bindings
|
54
|
+
# @return [Array<Google::Iam::V1::Binding>]
|
55
|
+
# Associates a list of `members` to a `role`.
|
56
|
+
# Multiple `bindings` must not be specified for the same `role`.
|
57
|
+
# `bindings` with no members will result in an error.
|
58
|
+
# @!attribute [rw] etag
|
59
|
+
# @return [String]
|
60
|
+
# `etag` is used for optimistic concurrency control as a way to help
|
61
|
+
# prevent simultaneous updates of a policy from overwriting each other.
|
62
|
+
# It is strongly suggested that systems make use of the `etag` in the
|
63
|
+
# read-modify-write cycle to perform policy updates in order to avoid race
|
64
|
+
# conditions: An `etag` is returned in the response to `getIamPolicy`, and
|
65
|
+
# systems are expected to put that etag in the request to `setIamPolicy` to
|
66
|
+
# ensure that their change will be applied to the same version of the policy.
|
67
|
+
#
|
68
|
+
# If no `etag` is provided in the call to `setIamPolicy`, then the existing
|
69
|
+
# policy is overwritten blindly.
|
70
|
+
class Policy; end
|
71
|
+
|
72
|
+
# Associates `members` with a `role`.
|
73
|
+
# @!attribute [rw] role
|
74
|
+
# @return [String]
|
75
|
+
# Role that is assigned to `members`.
|
76
|
+
# For example, `roles/viewer`, `roles/editor`, or `roles/owner`.
|
77
|
+
# Required
|
78
|
+
# @!attribute [rw] members
|
79
|
+
# @return [Array<String>]
|
80
|
+
# Specifies the identities requesting access for a Cloud Platform resource.
|
81
|
+
# `members` can have the following values:
|
82
|
+
#
|
83
|
+
# * `allUsers`: A special identifier that represents anyone who is
|
84
|
+
# on the internet; with or without a Google account.
|
85
|
+
#
|
86
|
+
# * `allAuthenticatedUsers`: A special identifier that represents anyone
|
87
|
+
# who is authenticated with a Google account or a service account.
|
88
|
+
#
|
89
|
+
# * `user:{emailid}`: An email address that represents a specific Google
|
90
|
+
# account. For example, `alice@gmail.com` or `joe@example.com`.
|
91
|
+
#
|
92
|
+
#
|
93
|
+
# * `serviceAccount:{emailid}`: An email address that represents a service
|
94
|
+
# account. For example, `my-other-app@appspot.gserviceaccount.com`.
|
95
|
+
#
|
96
|
+
# * `group:{emailid}`: An email address that represents a Google group.
|
97
|
+
# For example, `admins@example.com`.
|
98
|
+
#
|
99
|
+
# * `domain:{domain}`: A Google Apps domain name that represents all the
|
100
|
+
# users of that domain. For example, `google.com` or `example.com`.
|
101
|
+
class Binding; end
|
102
|
+
end
|
103
|
+
end
|
104
|
+
end
|
@@ -0,0 +1,130 @@
|
|
1
|
+
# Copyright 2019 Google LLC
|
2
|
+
#
|
3
|
+
# Licensed under the Apache License, Version 2.0 (the "License");
|
4
|
+
# you may not use this file except in compliance with the License.
|
5
|
+
# You may obtain a copy of the License at
|
6
|
+
#
|
7
|
+
# https://www.apache.org/licenses/LICENSE-2.0
|
8
|
+
#
|
9
|
+
# Unless required by applicable law or agreed to in writing, software
|
10
|
+
# distributed under the License is distributed on an "AS IS" BASIS,
|
11
|
+
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
12
|
+
# See the License for the specific language governing permissions and
|
13
|
+
# limitations under the License.
|
14
|
+
|
15
|
+
|
16
|
+
module Google
|
17
|
+
module Protobuf
|
18
|
+
# `Any` contains an arbitrary serialized protocol buffer message along with a
|
19
|
+
# URL that describes the type of the serialized message.
|
20
|
+
#
|
21
|
+
# Protobuf library provides support to pack/unpack Any values in the form
|
22
|
+
# of utility functions or additional generated methods of the Any type.
|
23
|
+
#
|
24
|
+
# Example 1: Pack and unpack a message in C++.
|
25
|
+
#
|
26
|
+
# Foo foo = ...;
|
27
|
+
# Any any;
|
28
|
+
# any.PackFrom(foo);
|
29
|
+
# ...
|
30
|
+
# if (any.UnpackTo(&foo)) {
|
31
|
+
# ...
|
32
|
+
# }
|
33
|
+
#
|
34
|
+
# Example 2: Pack and unpack a message in Java.
|
35
|
+
#
|
36
|
+
# Foo foo = ...;
|
37
|
+
# Any any = Any.pack(foo);
|
38
|
+
# ...
|
39
|
+
# if (any.is(Foo.class)) {
|
40
|
+
# foo = any.unpack(Foo.class);
|
41
|
+
# }
|
42
|
+
#
|
43
|
+
# Example 3: Pack and unpack a message in Python.
|
44
|
+
#
|
45
|
+
# foo = Foo(...)
|
46
|
+
# any = Any()
|
47
|
+
# any.Pack(foo)
|
48
|
+
# ...
|
49
|
+
# if any.Is(Foo.DESCRIPTOR):
|
50
|
+
# any.Unpack(foo)
|
51
|
+
# ...
|
52
|
+
#
|
53
|
+
# Example 4: Pack and unpack a message in Go
|
54
|
+
#
|
55
|
+
# foo := &pb.Foo{...}
|
56
|
+
# any, err := ptypes.MarshalAny(foo)
|
57
|
+
# ...
|
58
|
+
# foo := &pb.Foo{}
|
59
|
+
# if err := ptypes.UnmarshalAny(any, foo); err != nil {
|
60
|
+
# ...
|
61
|
+
# }
|
62
|
+
#
|
63
|
+
# The pack methods provided by protobuf library will by default use
|
64
|
+
# 'type.googleapis.com/full.type.name' as the type URL and the unpack
|
65
|
+
# methods only use the fully qualified type name after the last '/'
|
66
|
+
# in the type URL, for example "foo.bar.com/x/y.z" will yield type
|
67
|
+
# name "y.z".
|
68
|
+
#
|
69
|
+
#
|
70
|
+
# = JSON
|
71
|
+
#
|
72
|
+
# The JSON representation of an `Any` value uses the regular
|
73
|
+
# representation of the deserialized, embedded message, with an
|
74
|
+
# additional field `@type` which contains the type URL. Example:
|
75
|
+
#
|
76
|
+
# package google.profile;
|
77
|
+
# message Person {
|
78
|
+
# string first_name = 1;
|
79
|
+
# string last_name = 2;
|
80
|
+
# }
|
81
|
+
#
|
82
|
+
# {
|
83
|
+
# "@type": "type.googleapis.com/google.profile.Person",
|
84
|
+
# "firstName": <string>,
|
85
|
+
# "lastName": <string>
|
86
|
+
# }
|
87
|
+
#
|
88
|
+
# If the embedded message type is well-known and has a custom JSON
|
89
|
+
# representation, that representation will be embedded adding a field
|
90
|
+
# `value` which holds the custom JSON in addition to the `@type`
|
91
|
+
# field. Example (for message {Google::Protobuf::Duration}):
|
92
|
+
#
|
93
|
+
# {
|
94
|
+
# "@type": "type.googleapis.com/google.protobuf.Duration",
|
95
|
+
# "value": "1.212s"
|
96
|
+
# }
|
97
|
+
# @!attribute [rw] type_url
|
98
|
+
# @return [String]
|
99
|
+
# A URL/resource name that uniquely identifies the type of the serialized
|
100
|
+
# protocol buffer message. The last segment of the URL's path must represent
|
101
|
+
# the fully qualified name of the type (as in
|
102
|
+
# `path/google.protobuf.Duration`). The name should be in a canonical form
|
103
|
+
# (e.g., leading "." is not accepted).
|
104
|
+
#
|
105
|
+
# In practice, teams usually precompile into the binary all types that they
|
106
|
+
# expect it to use in the context of Any. However, for URLs which use the
|
107
|
+
# scheme `http`, `https`, or no scheme, one can optionally set up a type
|
108
|
+
# server that maps type URLs to message definitions as follows:
|
109
|
+
#
|
110
|
+
# * If no scheme is provided, `https` is assumed.
|
111
|
+
# * An HTTP GET on the URL must yield a {Google::Protobuf::Type}
|
112
|
+
# value in binary format, or produce an error.
|
113
|
+
# * Applications are allowed to cache lookup results based on the
|
114
|
+
# URL, or have them precompiled into a binary to avoid any
|
115
|
+
# lookup. Therefore, binary compatibility needs to be preserved
|
116
|
+
# on changes to types. (Use versioned type names to manage
|
117
|
+
# breaking changes.)
|
118
|
+
#
|
119
|
+
# Note: this functionality is not currently available in the official
|
120
|
+
# protobuf release, and it is not used for type URLs beginning with
|
121
|
+
# type.googleapis.com.
|
122
|
+
#
|
123
|
+
# Schemes other than `http`, `https` (or the empty scheme) might be
|
124
|
+
# used with implementation specific semantics.
|
125
|
+
# @!attribute [rw] value
|
126
|
+
# @return [String]
|
127
|
+
# Must be a valid serialized protocol buffer of the above specified type.
|
128
|
+
class Any; end
|
129
|
+
end
|
130
|
+
end
|
@@ -0,0 +1,91 @@
|
|
1
|
+
# Copyright 2019 Google LLC
|
2
|
+
#
|
3
|
+
# Licensed under the Apache License, Version 2.0 (the "License");
|
4
|
+
# you may not use this file except in compliance with the License.
|
5
|
+
# You may obtain a copy of the License at
|
6
|
+
#
|
7
|
+
# https://www.apache.org/licenses/LICENSE-2.0
|
8
|
+
#
|
9
|
+
# Unless required by applicable law or agreed to in writing, software
|
10
|
+
# distributed under the License is distributed on an "AS IS" BASIS,
|
11
|
+
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
12
|
+
# See the License for the specific language governing permissions and
|
13
|
+
# limitations under the License.
|
14
|
+
|
15
|
+
|
16
|
+
module Google
|
17
|
+
module Protobuf
|
18
|
+
# A Duration represents a signed, fixed-length span of time represented
|
19
|
+
# as a count of seconds and fractions of seconds at nanosecond
|
20
|
+
# resolution. It is independent of any calendar and concepts like "day"
|
21
|
+
# or "month". It is related to Timestamp in that the difference between
|
22
|
+
# two Timestamp values is a Duration and it can be added or subtracted
|
23
|
+
# from a Timestamp. Range is approximately +-10,000 years.
|
24
|
+
#
|
25
|
+
# = Examples
|
26
|
+
#
|
27
|
+
# Example 1: Compute Duration from two Timestamps in pseudo code.
|
28
|
+
#
|
29
|
+
# Timestamp start = ...;
|
30
|
+
# Timestamp end = ...;
|
31
|
+
# Duration duration = ...;
|
32
|
+
#
|
33
|
+
# duration.seconds = end.seconds - start.seconds;
|
34
|
+
# duration.nanos = end.nanos - start.nanos;
|
35
|
+
#
|
36
|
+
# if (duration.seconds < 0 && duration.nanos > 0) {
|
37
|
+
# duration.seconds += 1;
|
38
|
+
# duration.nanos -= 1000000000;
|
39
|
+
# } else if (durations.seconds > 0 && duration.nanos < 0) {
|
40
|
+
# duration.seconds -= 1;
|
41
|
+
# duration.nanos += 1000000000;
|
42
|
+
# }
|
43
|
+
#
|
44
|
+
# Example 2: Compute Timestamp from Timestamp + Duration in pseudo code.
|
45
|
+
#
|
46
|
+
# Timestamp start = ...;
|
47
|
+
# Duration duration = ...;
|
48
|
+
# Timestamp end = ...;
|
49
|
+
#
|
50
|
+
# end.seconds = start.seconds + duration.seconds;
|
51
|
+
# end.nanos = start.nanos + duration.nanos;
|
52
|
+
#
|
53
|
+
# if (end.nanos < 0) {
|
54
|
+
# end.seconds -= 1;
|
55
|
+
# end.nanos += 1000000000;
|
56
|
+
# } else if (end.nanos >= 1000000000) {
|
57
|
+
# end.seconds += 1;
|
58
|
+
# end.nanos -= 1000000000;
|
59
|
+
# }
|
60
|
+
#
|
61
|
+
# Example 3: Compute Duration from datetime.timedelta in Python.
|
62
|
+
#
|
63
|
+
# td = datetime.timedelta(days=3, minutes=10)
|
64
|
+
# duration = Duration()
|
65
|
+
# duration.FromTimedelta(td)
|
66
|
+
#
|
67
|
+
# = JSON Mapping
|
68
|
+
#
|
69
|
+
# In JSON format, the Duration type is encoded as a string rather than an
|
70
|
+
# object, where the string ends in the suffix "s" (indicating seconds) and
|
71
|
+
# is preceded by the number of seconds, with nanoseconds expressed as
|
72
|
+
# fractional seconds. For example, 3 seconds with 0 nanoseconds should be
|
73
|
+
# encoded in JSON format as "3s", while 3 seconds and 1 nanosecond should
|
74
|
+
# be expressed in JSON format as "3.000000001s", and 3 seconds and 1
|
75
|
+
# microsecond should be expressed in JSON format as "3.000001s".
|
76
|
+
# @!attribute [rw] seconds
|
77
|
+
# @return [Integer]
|
78
|
+
# Signed seconds of the span of time. Must be from -315,576,000,000
|
79
|
+
# to +315,576,000,000 inclusive. Note: these bounds are computed from:
|
80
|
+
# 60 sec/min * 60 min/hr * 24 hr/day * 365.25 days/year * 10000 years
|
81
|
+
# @!attribute [rw] nanos
|
82
|
+
# @return [Integer]
|
83
|
+
# Signed fractions of a second at nanosecond resolution of the span
|
84
|
+
# of time. Durations less than one second are represented with a 0
|
85
|
+
# `seconds` field and a positive or negative `nanos` field. For durations
|
86
|
+
# of one second or more, a non-zero value for the `nanos` field must be
|
87
|
+
# of the same sign as the `seconds` field. Must be from -999,999,999
|
88
|
+
# to +999,999,999 inclusive.
|
89
|
+
class Duration; end
|
90
|
+
end
|
91
|
+
end
|
@@ -0,0 +1,29 @@
|
|
1
|
+
# Copyright 2019 Google LLC
|
2
|
+
#
|
3
|
+
# Licensed under the Apache License, Version 2.0 (the "License");
|
4
|
+
# you may not use this file except in compliance with the License.
|
5
|
+
# You may obtain a copy of the License at
|
6
|
+
#
|
7
|
+
# https://www.apache.org/licenses/LICENSE-2.0
|
8
|
+
#
|
9
|
+
# Unless required by applicable law or agreed to in writing, software
|
10
|
+
# distributed under the License is distributed on an "AS IS" BASIS,
|
11
|
+
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
12
|
+
# See the License for the specific language governing permissions and
|
13
|
+
# limitations under the License.
|
14
|
+
|
15
|
+
|
16
|
+
module Google
|
17
|
+
module Protobuf
|
18
|
+
# A generic empty message that you can re-use to avoid defining duplicated
|
19
|
+
# empty messages in your APIs. A typical example is to use it as the request
|
20
|
+
# or the response type of an API method. For instance:
|
21
|
+
#
|
22
|
+
# service Foo {
|
23
|
+
# rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty);
|
24
|
+
# }
|
25
|
+
#
|
26
|
+
# The JSON representation for `Empty` is empty JSON object `{}`.
|
27
|
+
class Empty; end
|
28
|
+
end
|
29
|
+
end
|
@@ -0,0 +1,230 @@
|
|
1
|
+
# Copyright 2019 Google LLC
|
2
|
+
#
|
3
|
+
# Licensed under the Apache License, Version 2.0 (the "License");
|
4
|
+
# you may not use this file except in compliance with the License.
|
5
|
+
# You may obtain a copy of the License at
|
6
|
+
#
|
7
|
+
# https://www.apache.org/licenses/LICENSE-2.0
|
8
|
+
#
|
9
|
+
# Unless required by applicable law or agreed to in writing, software
|
10
|
+
# distributed under the License is distributed on an "AS IS" BASIS,
|
11
|
+
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
12
|
+
# See the License for the specific language governing permissions and
|
13
|
+
# limitations under the License.
|
14
|
+
|
15
|
+
|
16
|
+
module Google
|
17
|
+
module Protobuf
|
18
|
+
# `FieldMask` represents a set of symbolic field paths, for example:
|
19
|
+
#
|
20
|
+
# paths: "f.a"
|
21
|
+
# paths: "f.b.d"
|
22
|
+
#
|
23
|
+
# Here `f` represents a field in some root message, `a` and `b`
|
24
|
+
# fields in the message found in `f`, and `d` a field found in the
|
25
|
+
# message in `f.b`.
|
26
|
+
#
|
27
|
+
# Field masks are used to specify a subset of fields that should be
|
28
|
+
# returned by a get operation or modified by an update operation.
|
29
|
+
# Field masks also have a custom JSON encoding (see below).
|
30
|
+
#
|
31
|
+
# = Field Masks in Projections
|
32
|
+
#
|
33
|
+
# When used in the context of a projection, a response message or
|
34
|
+
# sub-message is filtered by the API to only contain those fields as
|
35
|
+
# specified in the mask. For example, if the mask in the previous
|
36
|
+
# example is applied to a response message as follows:
|
37
|
+
#
|
38
|
+
# f {
|
39
|
+
# a : 22
|
40
|
+
# b {
|
41
|
+
# d : 1
|
42
|
+
# x : 2
|
43
|
+
# }
|
44
|
+
# y : 13
|
45
|
+
# }
|
46
|
+
# z: 8
|
47
|
+
#
|
48
|
+
# The result will not contain specific values for fields x,y and z
|
49
|
+
# (their value will be set to the default, and omitted in proto text
|
50
|
+
# output):
|
51
|
+
#
|
52
|
+
#
|
53
|
+
# f {
|
54
|
+
# a : 22
|
55
|
+
# b {
|
56
|
+
# d : 1
|
57
|
+
# }
|
58
|
+
# }
|
59
|
+
#
|
60
|
+
# A repeated field is not allowed except at the last position of a
|
61
|
+
# paths string.
|
62
|
+
#
|
63
|
+
# If a FieldMask object is not present in a get operation, the
|
64
|
+
# operation applies to all fields (as if a FieldMask of all fields
|
65
|
+
# had been specified).
|
66
|
+
#
|
67
|
+
# Note that a field mask does not necessarily apply to the
|
68
|
+
# top-level response message. In case of a REST get operation, the
|
69
|
+
# field mask applies directly to the response, but in case of a REST
|
70
|
+
# list operation, the mask instead applies to each individual message
|
71
|
+
# in the returned resource list. In case of a REST custom method,
|
72
|
+
# other definitions may be used. Where the mask applies will be
|
73
|
+
# clearly documented together with its declaration in the API. In
|
74
|
+
# any case, the effect on the returned resource/resources is required
|
75
|
+
# behavior for APIs.
|
76
|
+
#
|
77
|
+
# = Field Masks in Update Operations
|
78
|
+
#
|
79
|
+
# A field mask in update operations specifies which fields of the
|
80
|
+
# targeted resource are going to be updated. The API is required
|
81
|
+
# to only change the values of the fields as specified in the mask
|
82
|
+
# and leave the others untouched. If a resource is passed in to
|
83
|
+
# describe the updated values, the API ignores the values of all
|
84
|
+
# fields not covered by the mask.
|
85
|
+
#
|
86
|
+
# If a repeated field is specified for an update operation, the existing
|
87
|
+
# repeated values in the target resource will be overwritten by the new values.
|
88
|
+
# Note that a repeated field is only allowed in the last position of a `paths`
|
89
|
+
# string.
|
90
|
+
#
|
91
|
+
# If a sub-message is specified in the last position of the field mask for an
|
92
|
+
# update operation, then the existing sub-message in the target resource is
|
93
|
+
# overwritten. Given the target message:
|
94
|
+
#
|
95
|
+
# f {
|
96
|
+
# b {
|
97
|
+
# d : 1
|
98
|
+
# x : 2
|
99
|
+
# }
|
100
|
+
# c : 1
|
101
|
+
# }
|
102
|
+
#
|
103
|
+
# And an update message:
|
104
|
+
#
|
105
|
+
# f {
|
106
|
+
# b {
|
107
|
+
# d : 10
|
108
|
+
# }
|
109
|
+
# }
|
110
|
+
#
|
111
|
+
# then if the field mask is:
|
112
|
+
#
|
113
|
+
# paths: "f.b"
|
114
|
+
#
|
115
|
+
# then the result will be:
|
116
|
+
#
|
117
|
+
# f {
|
118
|
+
# b {
|
119
|
+
# d : 10
|
120
|
+
# }
|
121
|
+
# c : 1
|
122
|
+
# }
|
123
|
+
#
|
124
|
+
# However, if the update mask was:
|
125
|
+
#
|
126
|
+
# paths: "f.b.d"
|
127
|
+
#
|
128
|
+
# then the result would be:
|
129
|
+
#
|
130
|
+
# f {
|
131
|
+
# b {
|
132
|
+
# d : 10
|
133
|
+
# x : 2
|
134
|
+
# }
|
135
|
+
# c : 1
|
136
|
+
# }
|
137
|
+
#
|
138
|
+
# In order to reset a field's value to the default, the field must
|
139
|
+
# be in the mask and set to the default value in the provided resource.
|
140
|
+
# Hence, in order to reset all fields of a resource, provide a default
|
141
|
+
# instance of the resource and set all fields in the mask, or do
|
142
|
+
# not provide a mask as described below.
|
143
|
+
#
|
144
|
+
# If a field mask is not present on update, the operation applies to
|
145
|
+
# all fields (as if a field mask of all fields has been specified).
|
146
|
+
# Note that in the presence of schema evolution, this may mean that
|
147
|
+
# fields the client does not know and has therefore not filled into
|
148
|
+
# the request will be reset to their default. If this is unwanted
|
149
|
+
# behavior, a specific service may require a client to always specify
|
150
|
+
# a field mask, producing an error if not.
|
151
|
+
#
|
152
|
+
# As with get operations, the location of the resource which
|
153
|
+
# describes the updated values in the request message depends on the
|
154
|
+
# operation kind. In any case, the effect of the field mask is
|
155
|
+
# required to be honored by the API.
|
156
|
+
#
|
157
|
+
# == Considerations for HTTP REST
|
158
|
+
#
|
159
|
+
# The HTTP kind of an update operation which uses a field mask must
|
160
|
+
# be set to PATCH instead of PUT in order to satisfy HTTP semantics
|
161
|
+
# (PUT must only be used for full updates).
|
162
|
+
#
|
163
|
+
# = JSON Encoding of Field Masks
|
164
|
+
#
|
165
|
+
# In JSON, a field mask is encoded as a single string where paths are
|
166
|
+
# separated by a comma. Fields name in each path are converted
|
167
|
+
# to/from lower-camel naming conventions.
|
168
|
+
#
|
169
|
+
# As an example, consider the following message declarations:
|
170
|
+
#
|
171
|
+
# message Profile {
|
172
|
+
# User user = 1;
|
173
|
+
# Photo photo = 2;
|
174
|
+
# }
|
175
|
+
# message User {
|
176
|
+
# string display_name = 1;
|
177
|
+
# string address = 2;
|
178
|
+
# }
|
179
|
+
#
|
180
|
+
# In proto a field mask for `Profile` may look as such:
|
181
|
+
#
|
182
|
+
# mask {
|
183
|
+
# paths: "user.display_name"
|
184
|
+
# paths: "photo"
|
185
|
+
# }
|
186
|
+
#
|
187
|
+
# In JSON, the same mask is represented as below:
|
188
|
+
#
|
189
|
+
# {
|
190
|
+
# mask: "user.displayName,photo"
|
191
|
+
# }
|
192
|
+
#
|
193
|
+
# = Field Masks and Oneof Fields
|
194
|
+
#
|
195
|
+
# Field masks treat fields in oneofs just as regular fields. Consider the
|
196
|
+
# following message:
|
197
|
+
#
|
198
|
+
# message SampleMessage {
|
199
|
+
# oneof test_oneof {
|
200
|
+
# string name = 4;
|
201
|
+
# SubMessage sub_message = 9;
|
202
|
+
# }
|
203
|
+
# }
|
204
|
+
#
|
205
|
+
# The field mask can be:
|
206
|
+
#
|
207
|
+
# mask {
|
208
|
+
# paths: "name"
|
209
|
+
# }
|
210
|
+
#
|
211
|
+
# Or:
|
212
|
+
#
|
213
|
+
# mask {
|
214
|
+
# paths: "sub_message"
|
215
|
+
# }
|
216
|
+
#
|
217
|
+
# Note that oneof type names ("test_oneof" in this case) cannot be used in
|
218
|
+
# paths.
|
219
|
+
#
|
220
|
+
# == Field Mask Verification
|
221
|
+
#
|
222
|
+
# The implementation of any API method which has a FieldMask type field in the
|
223
|
+
# request should verify the included field paths, and return an
|
224
|
+
# `INVALID_ARGUMENT` error if any path is duplicated or unmappable.
|
225
|
+
# @!attribute [rw] paths
|
226
|
+
# @return [Array<String>]
|
227
|
+
# The set of field mask paths.
|
228
|
+
class FieldMask; end
|
229
|
+
end
|
230
|
+
end
|