• Home
  • Line#
  • Scopes#
  • Navigate#
  • Raw
  • Download
1<html><body>
2<style>
3
4body, h1, h2, h3, div, span, p, pre, a {
5  margin: 0;
6  padding: 0;
7  border: 0;
8  font-weight: inherit;
9  font-style: inherit;
10  font-size: 100%;
11  font-family: inherit;
12  vertical-align: baseline;
13}
14
15body {
16  font-size: 13px;
17  padding: 1em;
18}
19
20h1 {
21  font-size: 26px;
22  margin-bottom: 1em;
23}
24
25h2 {
26  font-size: 24px;
27  margin-bottom: 1em;
28}
29
30h3 {
31  font-size: 20px;
32  margin-bottom: 1em;
33  margin-top: 1em;
34}
35
36pre, code {
37  line-height: 1.5;
38  font-family: Monaco, 'DejaVu Sans Mono', 'Bitstream Vera Sans Mono', 'Lucida Console', monospace;
39}
40
41pre {
42  margin-top: 0.5em;
43}
44
45h1, h2, h3, p {
46  font-family: Arial, sans serif;
47}
48
49h1, h2, h3 {
50  border-bottom: solid #CCC 1px;
51}
52
53.toc_element {
54  margin-top: 0.5em;
55}
56
57.firstline {
58  margin-left: 2 em;
59}
60
61.method  {
62  margin-top: 1em;
63  border: solid 1px #CCC;
64  padding: 1em;
65  background: #EEE;
66}
67
68.details {
69  font-weight: bold;
70  font-size: 14px;
71}
72
73</style>
74
75<h1><a href="runtimeconfig_v1beta1.html">Cloud Runtime Configuration API</a> . <a href="runtimeconfig_v1beta1.projects.html">projects</a> . <a href="runtimeconfig_v1beta1.projects.configs.html">configs</a> . <a href="runtimeconfig_v1beta1.projects.configs.variables.html">variables</a></h1>
76<h2>Instance Methods</h2>
77<p class="toc_element">
78  <code><a href="#create">create(parent, body, requestId=None, x__xgafv=None)</a></code></p>
79<p class="firstline">Creates a variable within the given configuration. You cannot create</p>
80<p class="toc_element">
81  <code><a href="#delete">delete(name, x__xgafv=None, recursive=None)</a></code></p>
82<p class="firstline">Deletes a variable or multiple variables.</p>
83<p class="toc_element">
84  <code><a href="#get">get(name, x__xgafv=None)</a></code></p>
85<p class="firstline">Gets information about a single variable.</p>
86<p class="toc_element">
87  <code><a href="#list">list(parent, pageSize=None, returnValues=None, x__xgafv=None, pageToken=None, filter=None)</a></code></p>
88<p class="firstline">Lists variables within given a configuration, matching any provided</p>
89<p class="toc_element">
90  <code><a href="#list_next">list_next(previous_request, previous_response)</a></code></p>
91<p class="firstline">Retrieves the next page of results.</p>
92<p class="toc_element">
93  <code><a href="#testIamPermissions">testIamPermissions(resource, body, x__xgafv=None)</a></code></p>
94<p class="firstline">Returns permissions that a caller has on the specified resource.</p>
95<p class="toc_element">
96  <code><a href="#update">update(name, body, x__xgafv=None)</a></code></p>
97<p class="firstline">Updates an existing variable with a new value.</p>
98<p class="toc_element">
99  <code><a href="#watch">watch(name, body, x__xgafv=None)</a></code></p>
100<p class="firstline">Watches a specific variable and waits for a change in the variable's value.</p>
101<h3>Method Details</h3>
102<div class="method">
103    <code class="details" id="create">create(parent, body, requestId=None, x__xgafv=None)</code>
104  <pre>Creates a variable within the given configuration. You cannot create
105a variable with a name that is a prefix of an existing variable name, or a
106name that has an existing variable name as a prefix.
107
108To learn more about creating a variable, read the
109[Setting and Getting
110Data](/deployment-manager/runtime-configurator/set-and-get-variables)
111documentation.
112
113Args:
114  parent: string, The path to the RutimeConfig resource that this variable should belong to.
115The configuration must exist beforehand; the path must be in the format:
116
117`projects/[PROJECT_ID]/configs/[CONFIG_NAME]` (required)
118  body: object, The request body. (required)
119    The object takes the form of:
120
121{ # Describes a single variable within a RuntimeConfig resource.
122    # The name denotes the hierarchical variable name. For example,
123    # `ports/serving_port` is a valid variable name. The variable value is an
124    # opaque string and only leaf variables can have values (that is, variables
125    # that do not have any child variables).
126  "text": "A String", # The string value of the variable. The length of the value must be less
127      # than 4096 bytes. Empty values are also accepted. For example,
128      # `text: "my text value"`. The string must be valid UTF-8.
129  "updateTime": "A String", # Output only. The time of the last variable update.
130      # Timestamp will be UTC timestamp.
131  "state": "A String", # Output only. The current state of the variable. The variable state
132      # indicates the outcome of the `variables().watch` call and is visible
133      # through the `get` and `list` calls.
134  "value": "A String", # The binary value of the variable. The length of the value must be less
135      # than 4096 bytes. Empty values are also accepted. The value must be
136      # base64 encoded, and must comply with IETF RFC4648
137      # (https://www.ietf.org/rfc/rfc4648.txt). Only one of `value` or `text`
138      # can be set.
139  "name": "A String", # The name of the variable resource, in the format:
140      #
141      #     projects/[PROJECT_ID]/configs/[CONFIG_NAME]/variables/[VARIABLE_NAME]
142      #
143      # The `[PROJECT_ID]` must be a valid project ID, `[CONFIG_NAME]` must be a
144      # valid RuntimeConfig resource and `[VARIABLE_NAME]` follows Unix file system
145      # file path naming.
146      #
147      # The `[VARIABLE_NAME]` can contain ASCII letters, numbers, slashes and
148      # dashes. Slashes are used as path element separators and are not part of the
149      # `[VARIABLE_NAME]` itself, so `[VARIABLE_NAME]` must contain at least one
150      # non-slash character. Multiple slashes are coalesced into single slash
151      # character. Each path segment should match
152      # [0-9A-Za-z](?:[_.A-Za-z0-9-]{0,62}[_.A-Za-z0-9])? regular expression.
153      # The length of a `[VARIABLE_NAME]` must be less than 256 characters.
154      #
155      # Once you create a variable, you cannot change the variable name.
156}
157
158  requestId: string, An optional but recommended unique `request_id`. If the server
159receives two `create()` requests  with the same
160`request_id`, then the second request will be ignored and the
161first resource created and stored in the backend is returned.
162Empty `request_id` fields are ignored.
163
164It is responsibility of the client to ensure uniqueness of the
165`request_id` strings.
166
167`request_id` strings are limited to 64 characters.
168  x__xgafv: string, V1 error format.
169    Allowed values
170      1 - v1 error format
171      2 - v2 error format
172
173Returns:
174  An object of the form:
175
176    { # Describes a single variable within a RuntimeConfig resource.
177      # The name denotes the hierarchical variable name. For example,
178      # `ports/serving_port` is a valid variable name. The variable value is an
179      # opaque string and only leaf variables can have values (that is, variables
180      # that do not have any child variables).
181    "text": "A String", # The string value of the variable. The length of the value must be less
182        # than 4096 bytes. Empty values are also accepted. For example,
183        # `text: "my text value"`. The string must be valid UTF-8.
184    "updateTime": "A String", # Output only. The time of the last variable update.
185        # Timestamp will be UTC timestamp.
186    "state": "A String", # Output only. The current state of the variable. The variable state
187        # indicates the outcome of the `variables().watch` call and is visible
188        # through the `get` and `list` calls.
189    "value": "A String", # The binary value of the variable. The length of the value must be less
190        # than 4096 bytes. Empty values are also accepted. The value must be
191        # base64 encoded, and must comply with IETF RFC4648
192        # (https://www.ietf.org/rfc/rfc4648.txt). Only one of `value` or `text`
193        # can be set.
194    "name": "A String", # The name of the variable resource, in the format:
195        #
196        #     projects/[PROJECT_ID]/configs/[CONFIG_NAME]/variables/[VARIABLE_NAME]
197        #
198        # The `[PROJECT_ID]` must be a valid project ID, `[CONFIG_NAME]` must be a
199        # valid RuntimeConfig resource and `[VARIABLE_NAME]` follows Unix file system
200        # file path naming.
201        #
202        # The `[VARIABLE_NAME]` can contain ASCII letters, numbers, slashes and
203        # dashes. Slashes are used as path element separators and are not part of the
204        # `[VARIABLE_NAME]` itself, so `[VARIABLE_NAME]` must contain at least one
205        # non-slash character. Multiple slashes are coalesced into single slash
206        # character. Each path segment should match
207        # [0-9A-Za-z](?:[_.A-Za-z0-9-]{0,62}[_.A-Za-z0-9])? regular expression.
208        # The length of a `[VARIABLE_NAME]` must be less than 256 characters.
209        #
210        # Once you create a variable, you cannot change the variable name.
211  }</pre>
212</div>
213
214<div class="method">
215    <code class="details" id="delete">delete(name, x__xgafv=None, recursive=None)</code>
216  <pre>Deletes a variable or multiple variables.
217
218If you specify a variable name, then that variable is deleted. If you
219specify a prefix and `recursive` is true, then all variables with that
220prefix are deleted. You must set a `recursive` to true if you delete
221variables by prefix.
222
223Args:
224  name: string, The name of the variable to delete, in the format:
225
226`projects/[PROJECT_ID]/configs/[CONFIG_NAME]/variables/[VARIABLE_NAME]` (required)
227  x__xgafv: string, V1 error format.
228    Allowed values
229      1 - v1 error format
230      2 - v2 error format
231  recursive: boolean, Set to `true` to recursively delete multiple variables with the same
232prefix.
233
234Returns:
235  An object of the form:
236
237    { # A generic empty message that you can re-use to avoid defining duplicated
238      # empty messages in your APIs. A typical example is to use it as the request
239      # or the response type of an API method. For instance:
240      #
241      #     service Foo {
242      #       rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty);
243      #     }
244      #
245      # The JSON representation for `Empty` is empty JSON object `{}`.
246  }</pre>
247</div>
248
249<div class="method">
250    <code class="details" id="get">get(name, x__xgafv=None)</code>
251  <pre>Gets information about a single variable.
252
253Args:
254  name: string, The name of the variable to return, in the format:
255
256`projects/[PROJECT_ID]/configs/[CONFIG_NAME]/variables/[VARIBLE_NAME]` (required)
257  x__xgafv: string, V1 error format.
258    Allowed values
259      1 - v1 error format
260      2 - v2 error format
261
262Returns:
263  An object of the form:
264
265    { # Describes a single variable within a RuntimeConfig resource.
266      # The name denotes the hierarchical variable name. For example,
267      # `ports/serving_port` is a valid variable name. The variable value is an
268      # opaque string and only leaf variables can have values (that is, variables
269      # that do not have any child variables).
270    "text": "A String", # The string value of the variable. The length of the value must be less
271        # than 4096 bytes. Empty values are also accepted. For example,
272        # `text: "my text value"`. The string must be valid UTF-8.
273    "updateTime": "A String", # Output only. The time of the last variable update.
274        # Timestamp will be UTC timestamp.
275    "state": "A String", # Output only. The current state of the variable. The variable state
276        # indicates the outcome of the `variables().watch` call and is visible
277        # through the `get` and `list` calls.
278    "value": "A String", # The binary value of the variable. The length of the value must be less
279        # than 4096 bytes. Empty values are also accepted. The value must be
280        # base64 encoded, and must comply with IETF RFC4648
281        # (https://www.ietf.org/rfc/rfc4648.txt). Only one of `value` or `text`
282        # can be set.
283    "name": "A String", # The name of the variable resource, in the format:
284        #
285        #     projects/[PROJECT_ID]/configs/[CONFIG_NAME]/variables/[VARIABLE_NAME]
286        #
287        # The `[PROJECT_ID]` must be a valid project ID, `[CONFIG_NAME]` must be a
288        # valid RuntimeConfig resource and `[VARIABLE_NAME]` follows Unix file system
289        # file path naming.
290        #
291        # The `[VARIABLE_NAME]` can contain ASCII letters, numbers, slashes and
292        # dashes. Slashes are used as path element separators and are not part of the
293        # `[VARIABLE_NAME]` itself, so `[VARIABLE_NAME]` must contain at least one
294        # non-slash character. Multiple slashes are coalesced into single slash
295        # character. Each path segment should match
296        # [0-9A-Za-z](?:[_.A-Za-z0-9-]{0,62}[_.A-Za-z0-9])? regular expression.
297        # The length of a `[VARIABLE_NAME]` must be less than 256 characters.
298        #
299        # Once you create a variable, you cannot change the variable name.
300  }</pre>
301</div>
302
303<div class="method">
304    <code class="details" id="list">list(parent, pageSize=None, returnValues=None, x__xgafv=None, pageToken=None, filter=None)</code>
305  <pre>Lists variables within given a configuration, matching any provided
306filters. This only lists variable names, not the values, unless
307`return_values` is true, in which case only variables that user has IAM
308permission to GetVariable will be returned.
309
310Args:
311  parent: string, The path to the RuntimeConfig resource for which you want to list
312variables. The configuration must exist beforehand; the path must be in the
313format:
314
315`projects/[PROJECT_ID]/configs/[CONFIG_NAME]` (required)
316  pageSize: integer, Specifies the number of results to return per page. If there are fewer
317elements than the specified number, returns all elements.
318  returnValues: boolean, The flag indicates whether the user wants to return values of variables.
319If true, then only those variables that user has IAM GetVariable permission
320will be returned along with their values.
321  x__xgafv: string, V1 error format.
322    Allowed values
323      1 - v1 error format
324      2 - v2 error format
325  pageToken: string, Specifies a page token to use. Set `pageToken` to a `nextPageToken`
326returned by a previous list request to get the next page of results.
327  filter: string, Filters variables by matching the specified filter. For example:
328
329`projects/example-project/config/[CONFIG_NAME]/variables/example-variable`.
330
331Returns:
332  An object of the form:
333
334    { # Response for the `ListVariables()` method.
335    "nextPageToken": "A String", # This token allows you to get the next page of results for list requests.
336        # If the number of results is larger than `pageSize`, use the `nextPageToken`
337        # as a value for the query parameter `pageToken` in the next list request.
338        # Subsequent list requests will have their own `nextPageToken` to continue
339        # paging through the results
340    "variables": [ # A list of variables and their values. The order of returned variable
341        # objects is arbitrary.
342      { # Describes a single variable within a RuntimeConfig resource.
343          # The name denotes the hierarchical variable name. For example,
344          # `ports/serving_port` is a valid variable name. The variable value is an
345          # opaque string and only leaf variables can have values (that is, variables
346          # that do not have any child variables).
347        "text": "A String", # The string value of the variable. The length of the value must be less
348            # than 4096 bytes. Empty values are also accepted. For example,
349            # `text: "my text value"`. The string must be valid UTF-8.
350        "updateTime": "A String", # Output only. The time of the last variable update.
351            # Timestamp will be UTC timestamp.
352        "state": "A String", # Output only. The current state of the variable. The variable state
353            # indicates the outcome of the `variables().watch` call and is visible
354            # through the `get` and `list` calls.
355        "value": "A String", # The binary value of the variable. The length of the value must be less
356            # than 4096 bytes. Empty values are also accepted. The value must be
357            # base64 encoded, and must comply with IETF RFC4648
358            # (https://www.ietf.org/rfc/rfc4648.txt). Only one of `value` or `text`
359            # can be set.
360        "name": "A String", # The name of the variable resource, in the format:
361            #
362            #     projects/[PROJECT_ID]/configs/[CONFIG_NAME]/variables/[VARIABLE_NAME]
363            #
364            # The `[PROJECT_ID]` must be a valid project ID, `[CONFIG_NAME]` must be a
365            # valid RuntimeConfig resource and `[VARIABLE_NAME]` follows Unix file system
366            # file path naming.
367            #
368            # The `[VARIABLE_NAME]` can contain ASCII letters, numbers, slashes and
369            # dashes. Slashes are used as path element separators and are not part of the
370            # `[VARIABLE_NAME]` itself, so `[VARIABLE_NAME]` must contain at least one
371            # non-slash character. Multiple slashes are coalesced into single slash
372            # character. Each path segment should match
373            # [0-9A-Za-z](?:[_.A-Za-z0-9-]{0,62}[_.A-Za-z0-9])? regular expression.
374            # The length of a `[VARIABLE_NAME]` must be less than 256 characters.
375            #
376            # Once you create a variable, you cannot change the variable name.
377      },
378    ],
379  }</pre>
380</div>
381
382<div class="method">
383    <code class="details" id="list_next">list_next(previous_request, previous_response)</code>
384  <pre>Retrieves the next page of results.
385
386Args:
387  previous_request: The request for the previous page. (required)
388  previous_response: The response from the request for the previous page. (required)
389
390Returns:
391  A request object that you can call 'execute()' on to request the next
392  page. Returns None if there are no more items in the collection.
393    </pre>
394</div>
395
396<div class="method">
397    <code class="details" id="testIamPermissions">testIamPermissions(resource, body, x__xgafv=None)</code>
398  <pre>Returns permissions that a caller has on the specified resource.
399If the resource does not exist, this will return an empty set of
400permissions, not a NOT_FOUND error.
401
402Note: This operation is designed to be used for building permission-aware
403UIs and command-line tools, not for authorization checking. This operation
404may "fail open" without warning.
405
406Args:
407  resource: string, REQUIRED: The resource for which the policy detail is being requested.
408See the operation documentation for the appropriate value for this field. (required)
409  body: object, The request body. (required)
410    The object takes the form of:
411
412{ # Request message for `TestIamPermissions` method.
413    "permissions": [ # The set of permissions to check for the `resource`. Permissions with
414        # wildcards (such as '*' or 'storage.*') are not allowed. For more
415        # information see
416        # [IAM Overview](https://cloud.google.com/iam/docs/overview#permissions).
417      "A String",
418    ],
419  }
420
421  x__xgafv: string, V1 error format.
422    Allowed values
423      1 - v1 error format
424      2 - v2 error format
425
426Returns:
427  An object of the form:
428
429    { # Response message for `TestIamPermissions` method.
430    "permissions": [ # A subset of `TestPermissionsRequest.permissions` that the caller is
431        # allowed.
432      "A String",
433    ],
434  }</pre>
435</div>
436
437<div class="method">
438    <code class="details" id="update">update(name, body, x__xgafv=None)</code>
439  <pre>Updates an existing variable with a new value.
440
441Args:
442  name: string, The name of the variable to update, in the format:
443
444`projects/[PROJECT_ID]/configs/[CONFIG_NAME]/variables/[VARIABLE_NAME]` (required)
445  body: object, The request body. (required)
446    The object takes the form of:
447
448{ # Describes a single variable within a RuntimeConfig resource.
449    # The name denotes the hierarchical variable name. For example,
450    # `ports/serving_port` is a valid variable name. The variable value is an
451    # opaque string and only leaf variables can have values (that is, variables
452    # that do not have any child variables).
453  "text": "A String", # The string value of the variable. The length of the value must be less
454      # than 4096 bytes. Empty values are also accepted. For example,
455      # `text: "my text value"`. The string must be valid UTF-8.
456  "updateTime": "A String", # Output only. The time of the last variable update.
457      # Timestamp will be UTC timestamp.
458  "state": "A String", # Output only. The current state of the variable. The variable state
459      # indicates the outcome of the `variables().watch` call and is visible
460      # through the `get` and `list` calls.
461  "value": "A String", # The binary value of the variable. The length of the value must be less
462      # than 4096 bytes. Empty values are also accepted. The value must be
463      # base64 encoded, and must comply with IETF RFC4648
464      # (https://www.ietf.org/rfc/rfc4648.txt). Only one of `value` or `text`
465      # can be set.
466  "name": "A String", # The name of the variable resource, in the format:
467      #
468      #     projects/[PROJECT_ID]/configs/[CONFIG_NAME]/variables/[VARIABLE_NAME]
469      #
470      # The `[PROJECT_ID]` must be a valid project ID, `[CONFIG_NAME]` must be a
471      # valid RuntimeConfig resource and `[VARIABLE_NAME]` follows Unix file system
472      # file path naming.
473      #
474      # The `[VARIABLE_NAME]` can contain ASCII letters, numbers, slashes and
475      # dashes. Slashes are used as path element separators and are not part of the
476      # `[VARIABLE_NAME]` itself, so `[VARIABLE_NAME]` must contain at least one
477      # non-slash character. Multiple slashes are coalesced into single slash
478      # character. Each path segment should match
479      # [0-9A-Za-z](?:[_.A-Za-z0-9-]{0,62}[_.A-Za-z0-9])? regular expression.
480      # The length of a `[VARIABLE_NAME]` must be less than 256 characters.
481      #
482      # Once you create a variable, you cannot change the variable name.
483}
484
485  x__xgafv: string, V1 error format.
486    Allowed values
487      1 - v1 error format
488      2 - v2 error format
489
490Returns:
491  An object of the form:
492
493    { # Describes a single variable within a RuntimeConfig resource.
494      # The name denotes the hierarchical variable name. For example,
495      # `ports/serving_port` is a valid variable name. The variable value is an
496      # opaque string and only leaf variables can have values (that is, variables
497      # that do not have any child variables).
498    "text": "A String", # The string value of the variable. The length of the value must be less
499        # than 4096 bytes. Empty values are also accepted. For example,
500        # `text: "my text value"`. The string must be valid UTF-8.
501    "updateTime": "A String", # Output only. The time of the last variable update.
502        # Timestamp will be UTC timestamp.
503    "state": "A String", # Output only. The current state of the variable. The variable state
504        # indicates the outcome of the `variables().watch` call and is visible
505        # through the `get` and `list` calls.
506    "value": "A String", # The binary value of the variable. The length of the value must be less
507        # than 4096 bytes. Empty values are also accepted. The value must be
508        # base64 encoded, and must comply with IETF RFC4648
509        # (https://www.ietf.org/rfc/rfc4648.txt). Only one of `value` or `text`
510        # can be set.
511    "name": "A String", # The name of the variable resource, in the format:
512        #
513        #     projects/[PROJECT_ID]/configs/[CONFIG_NAME]/variables/[VARIABLE_NAME]
514        #
515        # The `[PROJECT_ID]` must be a valid project ID, `[CONFIG_NAME]` must be a
516        # valid RuntimeConfig resource and `[VARIABLE_NAME]` follows Unix file system
517        # file path naming.
518        #
519        # The `[VARIABLE_NAME]` can contain ASCII letters, numbers, slashes and
520        # dashes. Slashes are used as path element separators and are not part of the
521        # `[VARIABLE_NAME]` itself, so `[VARIABLE_NAME]` must contain at least one
522        # non-slash character. Multiple slashes are coalesced into single slash
523        # character. Each path segment should match
524        # [0-9A-Za-z](?:[_.A-Za-z0-9-]{0,62}[_.A-Za-z0-9])? regular expression.
525        # The length of a `[VARIABLE_NAME]` must be less than 256 characters.
526        #
527        # Once you create a variable, you cannot change the variable name.
528  }</pre>
529</div>
530
531<div class="method">
532    <code class="details" id="watch">watch(name, body, x__xgafv=None)</code>
533  <pre>Watches a specific variable and waits for a change in the variable's value.
534When there is a change, this method returns the new value or times out.
535
536If a variable is deleted while being watched, the `variableState` state is
537set to `DELETED` and the method returns the last known variable `value`.
538
539If you set the deadline for watching to a larger value than internal
540timeout (60 seconds), the current variable value is returned and the
541`variableState` will be `VARIABLE_STATE_UNSPECIFIED`.
542
543To learn more about creating a watcher, read the
544[Watching a Variable for
545Changes](/deployment-manager/runtime-configurator/watching-a-variable)
546documentation.
547
548Args:
549  name: string, The name of the variable to watch, in the format:
550
551`projects/[PROJECT_ID]/configs/[CONFIG_NAME]` (required)
552  body: object, The request body. (required)
553    The object takes the form of:
554
555{ # Request for the `WatchVariable()` method.
556    "newerThan": "A String", # If specified, checks the current timestamp of the variable and if the
557        # current timestamp is newer than `newerThan` timestamp, the method returns
558        # immediately.
559        #
560        # If not specified or the variable has an older timestamp, the watcher waits
561        # for a the value to change before returning.
562  }
563
564  x__xgafv: string, V1 error format.
565    Allowed values
566      1 - v1 error format
567      2 - v2 error format
568
569Returns:
570  An object of the form:
571
572    { # Describes a single variable within a RuntimeConfig resource.
573      # The name denotes the hierarchical variable name. For example,
574      # `ports/serving_port` is a valid variable name. The variable value is an
575      # opaque string and only leaf variables can have values (that is, variables
576      # that do not have any child variables).
577    "text": "A String", # The string value of the variable. The length of the value must be less
578        # than 4096 bytes. Empty values are also accepted. For example,
579        # `text: "my text value"`. The string must be valid UTF-8.
580    "updateTime": "A String", # Output only. The time of the last variable update.
581        # Timestamp will be UTC timestamp.
582    "state": "A String", # Output only. The current state of the variable. The variable state
583        # indicates the outcome of the `variables().watch` call and is visible
584        # through the `get` and `list` calls.
585    "value": "A String", # The binary value of the variable. The length of the value must be less
586        # than 4096 bytes. Empty values are also accepted. The value must be
587        # base64 encoded, and must comply with IETF RFC4648
588        # (https://www.ietf.org/rfc/rfc4648.txt). Only one of `value` or `text`
589        # can be set.
590    "name": "A String", # The name of the variable resource, in the format:
591        #
592        #     projects/[PROJECT_ID]/configs/[CONFIG_NAME]/variables/[VARIABLE_NAME]
593        #
594        # The `[PROJECT_ID]` must be a valid project ID, `[CONFIG_NAME]` must be a
595        # valid RuntimeConfig resource and `[VARIABLE_NAME]` follows Unix file system
596        # file path naming.
597        #
598        # The `[VARIABLE_NAME]` can contain ASCII letters, numbers, slashes and
599        # dashes. Slashes are used as path element separators and are not part of the
600        # `[VARIABLE_NAME]` itself, so `[VARIABLE_NAME]` must contain at least one
601        # non-slash character. Multiple slashes are coalesced into single slash
602        # character. Each path segment should match
603        # [0-9A-Za-z](?:[_.A-Za-z0-9-]{0,62}[_.A-Za-z0-9])? regular expression.
604        # The length of a `[VARIABLE_NAME]` must be less than 256 characters.
605        #
606        # Once you create a variable, you cannot change the variable name.
607  }</pre>
608</div>
609
610</body></html>