Merge pull request #27 from kubernetes-incubator/gen
Update generated client
This commit is contained in:
commit
76bd09d515
@ -3,7 +3,7 @@
|
||||
## Properties
|
||||
Name | Type | Description | Notes
|
||||
------------ | ------------- | ------------- | -------------
|
||||
**data** | **dict(str, list[int])** | Data contains the secret data. Each key must be a valid DNS_SUBDOMAIN or leading dot followed by valid DNS_SUBDOMAIN. The serialized form of the secret data is a base64 encoded string, representing the arbitrary (possibly non-string) data value here. Described in https://tools.ietf.org/html/rfc4648#section-4 | [optional]
|
||||
**data** | **dict(str, str)** | Data contains the secret data. Each key must be a valid DNS_SUBDOMAIN or leading dot followed by valid DNS_SUBDOMAIN. The serialized form of the secret data is a base64 encoded string, representing the arbitrary (possibly non-string) data value here. Described in https://tools.ietf.org/html/rfc4648#section-4 | [optional]
|
||||
**metadata** | [**V1ObjectMeta**](V1ObjectMeta.md) | Standard object's metadata. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#metadata | [optional]
|
||||
**string_data** | **dict(str, str)** | stringData allows specifying non-binary secret data in string form. It is provided as a write-only convenience method. All keys and values are merged into the data field on write, overwriting any existing values. It is never output when reading from the API. | [optional]
|
||||
**type** | **str** | Used to facilitate programmatic handling of secret data. | [optional]
|
||||
|
||||
@ -42,7 +42,7 @@ class V1Secret(object):
|
||||
and the value is json key in definition.
|
||||
"""
|
||||
self.swagger_types = {
|
||||
'data': 'dict(str, list[int])',
|
||||
'data': 'dict(str, str)',
|
||||
'metadata': 'V1ObjectMeta',
|
||||
'string_data': 'dict(str, str)',
|
||||
'type': 'str'
|
||||
@ -68,7 +68,7 @@ class V1Secret(object):
|
||||
Data contains the secret data. Each key must be a valid DNS_SUBDOMAIN or leading dot followed by valid DNS_SUBDOMAIN. The serialized form of the secret data is a base64 encoded string, representing the arbitrary (possibly non-string) data value here. Described in https://tools.ietf.org/html/rfc4648#section-4
|
||||
|
||||
:return: The data of this V1Secret.
|
||||
:rtype: dict(str, list[int])
|
||||
:rtype: dict(str, str)
|
||||
"""
|
||||
return self._data
|
||||
|
||||
@ -79,7 +79,7 @@ class V1Secret(object):
|
||||
Data contains the secret data. Each key must be a valid DNS_SUBDOMAIN or leading dot followed by valid DNS_SUBDOMAIN. The serialized form of the secret data is a base64 encoded string, representing the arbitrary (possibly non-string) data value here. Described in https://tools.ietf.org/html/rfc4648#section-4
|
||||
|
||||
:param data: The data of this V1Secret.
|
||||
:type: dict(str, list[int])
|
||||
:type: dict(str, str)
|
||||
"""
|
||||
|
||||
self._data = data
|
||||
|
||||
@ -34956,11 +34956,8 @@
|
||||
"description": "Data contains the secret data. Each key must be a valid DNS_SUBDOMAIN or leading dot followed by valid DNS_SUBDOMAIN. The serialized form of the secret data is a base64 encoded string, representing the arbitrary (possibly non-string) data value here. Described in https://tools.ietf.org/html/rfc4648#section-4",
|
||||
"type": "object",
|
||||
"additionalProperties": {
|
||||
"type": "array",
|
||||
"items": {
|
||||
"type": "integer",
|
||||
"format": "byte"
|
||||
}
|
||||
"type": "string",
|
||||
"format": "byte"
|
||||
}
|
||||
},
|
||||
"metadata": {
|
||||
|
||||
Loading…
Reference in New Issue
Block a user