docs: update docs/dyn (#1096)
This PR was generated using Autosynth. :rainbow:
Synth log will be available here:
https://source.cloud.google.com/results/invocations/6f0f288a-a1e8-4b2d-a85f-00b1c6150185/targets
- [ ] To automatically regenerate this PR, check this box.
Source-Link: https://github.com/googleapis/synthtool/commit/39b7149da4026765385403632db3c6f63db96b2c
Source-Link: https://github.com/googleapis/synthtool/commit/9a7d9fbb7045c34c9d3d22c1ff766eeae51f04c9
Source-Link: https://github.com/googleapis/synthtool/commit/dc9903a8c30c3662b6098f0e4a97f221d67268b2
Source-Link: https://github.com/googleapis/synthtool/commit/7fcc405a579d5d53a726ff3da1b7c8c08f0f2d58
Source-Link: https://github.com/googleapis/synthtool/commit/d5fc0bcf9ea9789c5b0e3154a9e3b29e5cea6116
Source-Link: https://github.com/googleapis/synthtool/commit/e89175cf074dccc4babb4eca66ae913696e47a71
Source-Link: https://github.com/googleapis/synthtool/commit/7d652819519dfa24da9e14548232e4aaba71a11c
Source-Link: https://github.com/googleapis/synthtool/commit/7db8a6c5ffb12a6e4c2f799c18f00f7f3d60e279
Source-Link: https://github.com/googleapis/synthtool/commit/1f1148d3c7a7a52f0c98077f976bd9b3c948ee2b
Source-Link: https://github.com/googleapis/synthtool/commit/2c8aecedd55b0480fb4e123b6e07fa5b12953862
Source-Link: https://github.com/googleapis/synthtool/commit/3d3e94c4e02370f307a9a200b0c743c3d8d19f29
Source-Link: https://github.com/googleapis/synthtool/commit/c7824ea48ff6d4d42dfae0849aec8a85acd90bd9
Source-Link: https://github.com/googleapis/synthtool/commit/ba9918cd22874245b55734f57470c719b577e591
Source-Link: https://github.com/googleapis/synthtool/commit/b19b401571e77192f8dd38eab5fb2300a0de9324
Source-Link: https://github.com/googleapis/synthtool/commit/6542bd723403513626f61642fc02ddca528409aa
diff --git a/docs/dyn/domainsrdap_v1.v1.html b/docs/dyn/domainsrdap_v1.v1.html
index 0029a0f..1139314 100644
--- a/docs/dyn/domainsrdap_v1.v1.html
+++ b/docs/dyn/domainsrdap_v1.v1.html
@@ -112,44 +112,44 @@
An object of the form:
{ # Response to a general RDAP query.
- "title": "A String", # Error title.
- "jsonResponse": { # Message that represents an arbitrary HTTP body. It should only be used for payload formats that can't be represented as JSON, such as raw binary or an HTML page. This message can be used both in streaming and non-streaming API methods in the request as well as the response. It can be used as a top-level request field, which is convenient if one wants to extract parameters from either the URL or HTTP template into the request fields and also want access to the raw HTTP body. Example: message GetResourceRequest { // A unique request id. string request_id = 1; // The raw HTTP body is bound to this field. google.api.HttpBody http_body = 2; } service ResourceService { rpc GetResource(GetResourceRequest) returns (google.api.HttpBody); rpc UpdateResource(google.api.HttpBody) returns (google.protobuf.Empty); } Example with streaming methods: service CaldavService { rpc GetCalendar(stream google.api.HttpBody) returns (stream google.api.HttpBody); rpc UpdateCalendar(stream google.api.HttpBody) returns (stream google.api.HttpBody); } Use of this type only changes how the request and response bodies are handled, all other features will continue to work unchanged. # HTTP response with content type set to "application/json+rdap".
- "extensions": [ # Application specific response metadata. Must be set in the first response for streaming APIs.
- {
- "a_key": "", # Properties of the object. Contains field @type with type URL.
- },
- ],
- "data": "A String", # The HTTP request/response body as raw binary.
- "contentType": "A String", # The HTTP Content-Type header value specifying the content type of the body.
- },
- "lang": "A String", # Error language code. Error response info fields are defined in [section 6 of RFC 7483](https://tools.ietf.org/html/rfc7483#section-6).
- "errorCode": 42, # Error HTTP code. Example: "501".
- "notices": [ # Notices applying to this response.
- { # Notices object defined in [section 4.3 of RFC 7483](https://tools.ietf.org/html/rfc7483#section-4.3).
- "title": "A String", # Title of a notice. Example: "Terms of Service".
- "links": [ # Link to a document containing more information.
- { # Links object defined in [section 4.2 of RFC 7483](https://tools.ietf.org/html/rfc7483#section-4.2).
- "hreflang": "A String", # Language code of a link. Example: "en".
- "href": "A String", # Target URL of a link. Example: "http://example.com/previous".
- "rel": "A String", # Relation type of a link. Example: "previous".
- "type": "A String", # Content type of the link. Example: "application/json".
- "title": "A String", # Title of this link. Example: "title".
- "value": "A String", # URL giving context for the link. Example: "http://example.com/current".
- "media": "A String", # Media type of the link destination. Example: "screen".
- },
- ],
- "description": [ # Description of the notice.
- "A String",
- ],
- "type": "A String", # Type values defined in [section 10.2.1 of RFC 7483](https://tools.ietf.org/html/rfc7483#section-10.2.1) specific to a whole response: "result set truncated due to authorization", "result set truncated due to excessive load", "result set truncated due to unexplainable reasons".
- },
- ],
"description": [ # Error description.
"A String",
],
"rdapConformance": [ # RDAP conformance level.
"A String",
],
+ "jsonResponse": { # Message that represents an arbitrary HTTP body. It should only be used for payload formats that can't be represented as JSON, such as raw binary or an HTML page. This message can be used both in streaming and non-streaming API methods in the request as well as the response. It can be used as a top-level request field, which is convenient if one wants to extract parameters from either the URL or HTTP template into the request fields and also want access to the raw HTTP body. Example: message GetResourceRequest { // A unique request id. string request_id = 1; // The raw HTTP body is bound to this field. google.api.HttpBody http_body = 2; } service ResourceService { rpc GetResource(GetResourceRequest) returns (google.api.HttpBody); rpc UpdateResource(google.api.HttpBody) returns (google.protobuf.Empty); } Example with streaming methods: service CaldavService { rpc GetCalendar(stream google.api.HttpBody) returns (stream google.api.HttpBody); rpc UpdateCalendar(stream google.api.HttpBody) returns (stream google.api.HttpBody); } Use of this type only changes how the request and response bodies are handled, all other features will continue to work unchanged. # HTTP response with content type set to "application/json+rdap".
+ "data": "A String", # The HTTP request/response body as raw binary.
+ "extensions": [ # Application specific response metadata. Must be set in the first response for streaming APIs.
+ {
+ "a_key": "", # Properties of the object. Contains field @type with type URL.
+ },
+ ],
+ "contentType": "A String", # The HTTP Content-Type header value specifying the content type of the body.
+ },
+ "notices": [ # Notices applying to this response.
+ { # Notices object defined in [section 4.3 of RFC 7483](https://tools.ietf.org/html/rfc7483#section-4.3).
+ "links": [ # Link to a document containing more information.
+ { # Links object defined in [section 4.2 of RFC 7483](https://tools.ietf.org/html/rfc7483#section-4.2).
+ "rel": "A String", # Relation type of a link. Example: "previous".
+ "href": "A String", # Target URL of a link. Example: "http://example.com/previous".
+ "type": "A String", # Content type of the link. Example: "application/json".
+ "value": "A String", # URL giving context for the link. Example: "http://example.com/current".
+ "media": "A String", # Media type of the link destination. Example: "screen".
+ "title": "A String", # Title of this link. Example: "title".
+ "hreflang": "A String", # Language code of a link. Example: "en".
+ },
+ ],
+ "type": "A String", # Type values defined in [section 10.2.1 of RFC 7483](https://tools.ietf.org/html/rfc7483#section-10.2.1) specific to a whole response: "result set truncated due to authorization", "result set truncated due to excessive load", "result set truncated due to unexplainable reasons".
+ "description": [ # Description of the notice.
+ "A String",
+ ],
+ "title": "A String", # Title of a notice. Example: "Terms of Service".
+ },
+ ],
+ "lang": "A String", # Error language code. Error response info fields are defined in [section 6 of RFC 7483](https://tools.ietf.org/html/rfc7483#section-6).
+ "errorCode": 42, # Error HTTP code. Example: "501".
+ "title": "A String", # Error title.
}</pre>
</div>
@@ -167,44 +167,44 @@
An object of the form:
{ # Response to a general RDAP query.
- "title": "A String", # Error title.
- "jsonResponse": { # Message that represents an arbitrary HTTP body. It should only be used for payload formats that can't be represented as JSON, such as raw binary or an HTML page. This message can be used both in streaming and non-streaming API methods in the request as well as the response. It can be used as a top-level request field, which is convenient if one wants to extract parameters from either the URL or HTTP template into the request fields and also want access to the raw HTTP body. Example: message GetResourceRequest { // A unique request id. string request_id = 1; // The raw HTTP body is bound to this field. google.api.HttpBody http_body = 2; } service ResourceService { rpc GetResource(GetResourceRequest) returns (google.api.HttpBody); rpc UpdateResource(google.api.HttpBody) returns (google.protobuf.Empty); } Example with streaming methods: service CaldavService { rpc GetCalendar(stream google.api.HttpBody) returns (stream google.api.HttpBody); rpc UpdateCalendar(stream google.api.HttpBody) returns (stream google.api.HttpBody); } Use of this type only changes how the request and response bodies are handled, all other features will continue to work unchanged. # HTTP response with content type set to "application/json+rdap".
- "extensions": [ # Application specific response metadata. Must be set in the first response for streaming APIs.
- {
- "a_key": "", # Properties of the object. Contains field @type with type URL.
- },
- ],
- "data": "A String", # The HTTP request/response body as raw binary.
- "contentType": "A String", # The HTTP Content-Type header value specifying the content type of the body.
- },
- "lang": "A String", # Error language code. Error response info fields are defined in [section 6 of RFC 7483](https://tools.ietf.org/html/rfc7483#section-6).
- "errorCode": 42, # Error HTTP code. Example: "501".
- "notices": [ # Notices applying to this response.
- { # Notices object defined in [section 4.3 of RFC 7483](https://tools.ietf.org/html/rfc7483#section-4.3).
- "title": "A String", # Title of a notice. Example: "Terms of Service".
- "links": [ # Link to a document containing more information.
- { # Links object defined in [section 4.2 of RFC 7483](https://tools.ietf.org/html/rfc7483#section-4.2).
- "hreflang": "A String", # Language code of a link. Example: "en".
- "href": "A String", # Target URL of a link. Example: "http://example.com/previous".
- "rel": "A String", # Relation type of a link. Example: "previous".
- "type": "A String", # Content type of the link. Example: "application/json".
- "title": "A String", # Title of this link. Example: "title".
- "value": "A String", # URL giving context for the link. Example: "http://example.com/current".
- "media": "A String", # Media type of the link destination. Example: "screen".
- },
- ],
- "description": [ # Description of the notice.
- "A String",
- ],
- "type": "A String", # Type values defined in [section 10.2.1 of RFC 7483](https://tools.ietf.org/html/rfc7483#section-10.2.1) specific to a whole response: "result set truncated due to authorization", "result set truncated due to excessive load", "result set truncated due to unexplainable reasons".
- },
- ],
"description": [ # Error description.
"A String",
],
"rdapConformance": [ # RDAP conformance level.
"A String",
],
+ "jsonResponse": { # Message that represents an arbitrary HTTP body. It should only be used for payload formats that can't be represented as JSON, such as raw binary or an HTML page. This message can be used both in streaming and non-streaming API methods in the request as well as the response. It can be used as a top-level request field, which is convenient if one wants to extract parameters from either the URL or HTTP template into the request fields and also want access to the raw HTTP body. Example: message GetResourceRequest { // A unique request id. string request_id = 1; // The raw HTTP body is bound to this field. google.api.HttpBody http_body = 2; } service ResourceService { rpc GetResource(GetResourceRequest) returns (google.api.HttpBody); rpc UpdateResource(google.api.HttpBody) returns (google.protobuf.Empty); } Example with streaming methods: service CaldavService { rpc GetCalendar(stream google.api.HttpBody) returns (stream google.api.HttpBody); rpc UpdateCalendar(stream google.api.HttpBody) returns (stream google.api.HttpBody); } Use of this type only changes how the request and response bodies are handled, all other features will continue to work unchanged. # HTTP response with content type set to "application/json+rdap".
+ "data": "A String", # The HTTP request/response body as raw binary.
+ "extensions": [ # Application specific response metadata. Must be set in the first response for streaming APIs.
+ {
+ "a_key": "", # Properties of the object. Contains field @type with type URL.
+ },
+ ],
+ "contentType": "A String", # The HTTP Content-Type header value specifying the content type of the body.
+ },
+ "notices": [ # Notices applying to this response.
+ { # Notices object defined in [section 4.3 of RFC 7483](https://tools.ietf.org/html/rfc7483#section-4.3).
+ "links": [ # Link to a document containing more information.
+ { # Links object defined in [section 4.2 of RFC 7483](https://tools.ietf.org/html/rfc7483#section-4.2).
+ "rel": "A String", # Relation type of a link. Example: "previous".
+ "href": "A String", # Target URL of a link. Example: "http://example.com/previous".
+ "type": "A String", # Content type of the link. Example: "application/json".
+ "value": "A String", # URL giving context for the link. Example: "http://example.com/current".
+ "media": "A String", # Media type of the link destination. Example: "screen".
+ "title": "A String", # Title of this link. Example: "title".
+ "hreflang": "A String", # Language code of a link. Example: "en".
+ },
+ ],
+ "type": "A String", # Type values defined in [section 10.2.1 of RFC 7483](https://tools.ietf.org/html/rfc7483#section-10.2.1) specific to a whole response: "result set truncated due to authorization", "result set truncated due to excessive load", "result set truncated due to unexplainable reasons".
+ "description": [ # Description of the notice.
+ "A String",
+ ],
+ "title": "A String", # Title of a notice. Example: "Terms of Service".
+ },
+ ],
+ "lang": "A String", # Error language code. Error response info fields are defined in [section 6 of RFC 7483](https://tools.ietf.org/html/rfc7483#section-6).
+ "errorCode": 42, # Error HTTP code. Example: "501".
+ "title": "A String", # Error title.
}</pre>
</div>
@@ -222,12 +222,12 @@
An object of the form:
{ # Message that represents an arbitrary HTTP body. It should only be used for payload formats that can't be represented as JSON, such as raw binary or an HTML page. This message can be used both in streaming and non-streaming API methods in the request as well as the response. It can be used as a top-level request field, which is convenient if one wants to extract parameters from either the URL or HTTP template into the request fields and also want access to the raw HTTP body. Example: message GetResourceRequest { // A unique request id. string request_id = 1; // The raw HTTP body is bound to this field. google.api.HttpBody http_body = 2; } service ResourceService { rpc GetResource(GetResourceRequest) returns (google.api.HttpBody); rpc UpdateResource(google.api.HttpBody) returns (google.protobuf.Empty); } Example with streaming methods: service CaldavService { rpc GetCalendar(stream google.api.HttpBody) returns (stream google.api.HttpBody); rpc UpdateCalendar(stream google.api.HttpBody) returns (stream google.api.HttpBody); } Use of this type only changes how the request and response bodies are handled, all other features will continue to work unchanged.
+ "data": "A String", # The HTTP request/response body as raw binary.
"extensions": [ # Application specific response metadata. Must be set in the first response for streaming APIs.
{
"a_key": "", # Properties of the object. Contains field @type with type URL.
},
],
- "data": "A String", # The HTTP request/response body as raw binary.
"contentType": "A String", # The HTTP Content-Type header value specifying the content type of the body.
}</pre>
</div>
@@ -246,12 +246,12 @@
An object of the form:
{ # Message that represents an arbitrary HTTP body. It should only be used for payload formats that can't be represented as JSON, such as raw binary or an HTML page. This message can be used both in streaming and non-streaming API methods in the request as well as the response. It can be used as a top-level request field, which is convenient if one wants to extract parameters from either the URL or HTTP template into the request fields and also want access to the raw HTTP body. Example: message GetResourceRequest { // A unique request id. string request_id = 1; // The raw HTTP body is bound to this field. google.api.HttpBody http_body = 2; } service ResourceService { rpc GetResource(GetResourceRequest) returns (google.api.HttpBody); rpc UpdateResource(google.api.HttpBody) returns (google.protobuf.Empty); } Example with streaming methods: service CaldavService { rpc GetCalendar(stream google.api.HttpBody) returns (stream google.api.HttpBody); rpc UpdateCalendar(stream google.api.HttpBody) returns (stream google.api.HttpBody); } Use of this type only changes how the request and response bodies are handled, all other features will continue to work unchanged.
+ "data": "A String", # The HTTP request/response body as raw binary.
"extensions": [ # Application specific response metadata. Must be set in the first response for streaming APIs.
{
"a_key": "", # Properties of the object. Contains field @type with type URL.
},
],
- "data": "A String", # The HTTP request/response body as raw binary.
"contentType": "A String", # The HTTP Content-Type header value specifying the content type of the body.
}</pre>
</div>
@@ -270,44 +270,44 @@
An object of the form:
{ # Response to a general RDAP query.
- "title": "A String", # Error title.
- "jsonResponse": { # Message that represents an arbitrary HTTP body. It should only be used for payload formats that can't be represented as JSON, such as raw binary or an HTML page. This message can be used both in streaming and non-streaming API methods in the request as well as the response. It can be used as a top-level request field, which is convenient if one wants to extract parameters from either the URL or HTTP template into the request fields and also want access to the raw HTTP body. Example: message GetResourceRequest { // A unique request id. string request_id = 1; // The raw HTTP body is bound to this field. google.api.HttpBody http_body = 2; } service ResourceService { rpc GetResource(GetResourceRequest) returns (google.api.HttpBody); rpc UpdateResource(google.api.HttpBody) returns (google.protobuf.Empty); } Example with streaming methods: service CaldavService { rpc GetCalendar(stream google.api.HttpBody) returns (stream google.api.HttpBody); rpc UpdateCalendar(stream google.api.HttpBody) returns (stream google.api.HttpBody); } Use of this type only changes how the request and response bodies are handled, all other features will continue to work unchanged. # HTTP response with content type set to "application/json+rdap".
- "extensions": [ # Application specific response metadata. Must be set in the first response for streaming APIs.
- {
- "a_key": "", # Properties of the object. Contains field @type with type URL.
- },
- ],
- "data": "A String", # The HTTP request/response body as raw binary.
- "contentType": "A String", # The HTTP Content-Type header value specifying the content type of the body.
- },
- "lang": "A String", # Error language code. Error response info fields are defined in [section 6 of RFC 7483](https://tools.ietf.org/html/rfc7483#section-6).
- "errorCode": 42, # Error HTTP code. Example: "501".
- "notices": [ # Notices applying to this response.
- { # Notices object defined in [section 4.3 of RFC 7483](https://tools.ietf.org/html/rfc7483#section-4.3).
- "title": "A String", # Title of a notice. Example: "Terms of Service".
- "links": [ # Link to a document containing more information.
- { # Links object defined in [section 4.2 of RFC 7483](https://tools.ietf.org/html/rfc7483#section-4.2).
- "hreflang": "A String", # Language code of a link. Example: "en".
- "href": "A String", # Target URL of a link. Example: "http://example.com/previous".
- "rel": "A String", # Relation type of a link. Example: "previous".
- "type": "A String", # Content type of the link. Example: "application/json".
- "title": "A String", # Title of this link. Example: "title".
- "value": "A String", # URL giving context for the link. Example: "http://example.com/current".
- "media": "A String", # Media type of the link destination. Example: "screen".
- },
- ],
- "description": [ # Description of the notice.
- "A String",
- ],
- "type": "A String", # Type values defined in [section 10.2.1 of RFC 7483](https://tools.ietf.org/html/rfc7483#section-10.2.1) specific to a whole response: "result set truncated due to authorization", "result set truncated due to excessive load", "result set truncated due to unexplainable reasons".
- },
- ],
"description": [ # Error description.
"A String",
],
"rdapConformance": [ # RDAP conformance level.
"A String",
],
+ "jsonResponse": { # Message that represents an arbitrary HTTP body. It should only be used for payload formats that can't be represented as JSON, such as raw binary or an HTML page. This message can be used both in streaming and non-streaming API methods in the request as well as the response. It can be used as a top-level request field, which is convenient if one wants to extract parameters from either the URL or HTTP template into the request fields and also want access to the raw HTTP body. Example: message GetResourceRequest { // A unique request id. string request_id = 1; // The raw HTTP body is bound to this field. google.api.HttpBody http_body = 2; } service ResourceService { rpc GetResource(GetResourceRequest) returns (google.api.HttpBody); rpc UpdateResource(google.api.HttpBody) returns (google.protobuf.Empty); } Example with streaming methods: service CaldavService { rpc GetCalendar(stream google.api.HttpBody) returns (stream google.api.HttpBody); rpc UpdateCalendar(stream google.api.HttpBody) returns (stream google.api.HttpBody); } Use of this type only changes how the request and response bodies are handled, all other features will continue to work unchanged. # HTTP response with content type set to "application/json+rdap".
+ "data": "A String", # The HTTP request/response body as raw binary.
+ "extensions": [ # Application specific response metadata. Must be set in the first response for streaming APIs.
+ {
+ "a_key": "", # Properties of the object. Contains field @type with type URL.
+ },
+ ],
+ "contentType": "A String", # The HTTP Content-Type header value specifying the content type of the body.
+ },
+ "notices": [ # Notices applying to this response.
+ { # Notices object defined in [section 4.3 of RFC 7483](https://tools.ietf.org/html/rfc7483#section-4.3).
+ "links": [ # Link to a document containing more information.
+ { # Links object defined in [section 4.2 of RFC 7483](https://tools.ietf.org/html/rfc7483#section-4.2).
+ "rel": "A String", # Relation type of a link. Example: "previous".
+ "href": "A String", # Target URL of a link. Example: "http://example.com/previous".
+ "type": "A String", # Content type of the link. Example: "application/json".
+ "value": "A String", # URL giving context for the link. Example: "http://example.com/current".
+ "media": "A String", # Media type of the link destination. Example: "screen".
+ "title": "A String", # Title of this link. Example: "title".
+ "hreflang": "A String", # Language code of a link. Example: "en".
+ },
+ ],
+ "type": "A String", # Type values defined in [section 10.2.1 of RFC 7483](https://tools.ietf.org/html/rfc7483#section-10.2.1) specific to a whole response: "result set truncated due to authorization", "result set truncated due to excessive load", "result set truncated due to unexplainable reasons".
+ "description": [ # Description of the notice.
+ "A String",
+ ],
+ "title": "A String", # Title of a notice. Example: "Terms of Service".
+ },
+ ],
+ "lang": "A String", # Error language code. Error response info fields are defined in [section 6 of RFC 7483](https://tools.ietf.org/html/rfc7483#section-6).
+ "errorCode": 42, # Error HTTP code. Example: "501".
+ "title": "A String", # Error title.
}</pre>
</div>