Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
36 commits
Select commit Hold shift + click to select a range
900418b
feat(aiplatform): update the api
yoshi-automation May 19, 2026
e49e2dd
feat(alloydb): update the api
yoshi-automation May 19, 2026
152fb01
feat(ces): update the api
yoshi-automation May 19, 2026
aef9526
feat(classroom): update the api
yoshi-automation May 19, 2026
eb70853
fix(clouderrorreporting): update the api
yoshi-automation May 19, 2026
8d3de00
feat(cloudidentity): update the api
yoshi-automation May 19, 2026
a7451e0
fix(cloudkms): update the api
yoshi-automation May 19, 2026
dcdef5c
feat(cloudtrace): update the api
yoshi-automation May 19, 2026
9b36f56
feat(compute): update the api
yoshi-automation May 19, 2026
efaa551
feat(contactcenterinsights): update the api
yoshi-automation May 19, 2026
b83ee78
feat(dataplex): update the api
yoshi-automation May 19, 2026
a843743
feat(datastream): update the api
yoshi-automation May 19, 2026
8b89067
feat(discoveryengine): update the api
yoshi-automation May 19, 2026
c1879ef
feat(dlp): update the api
yoshi-automation May 19, 2026
85166ba
feat(documentai): update the api
yoshi-automation May 19, 2026
7aa35d4
feat(firebaseml): update the api
yoshi-automation May 19, 2026
5f4a1a9
feat(gkehub): update the api
yoshi-automation May 19, 2026
bc36a9a
feat(gmail): update the api
yoshi-automation May 19, 2026
e74f64e
feat(health): update the api
yoshi-automation May 19, 2026
2e51fa2
feat(healthcare): update the api
yoshi-automation May 19, 2026
ee36960
feat(homegraph): update the api
yoshi-automation May 19, 2026
443eb0f
feat(merchantapi): update the api
yoshi-automation May 19, 2026
294a257
feat(migrationcenter): update the api
yoshi-automation May 19, 2026
b717094
feat(mybusinessaccountmanagement): update the api
yoshi-automation May 19, 2026
024a925
feat(netapp): update the api
yoshi-automation May 19, 2026
b7262f9
feat(networkconnectivity): update the api
yoshi-automation May 19, 2026
ff905db
feat(networkmanagement): update the api
yoshi-automation May 19, 2026
e628886
feat(networkservices): update the api
yoshi-automation May 19, 2026
0f819a1
feat(ondemandscanning): update the api
yoshi-automation May 19, 2026
7cf48d0
feat(oracledatabase): update the api
yoshi-automation May 19, 2026
ba1091b
feat(osconfig): update the api
yoshi-automation May 19, 2026
02f5d2e
feat(run): update the api
yoshi-automation May 19, 2026
be03e96
feat(tagmanager): update the api
yoshi-automation May 19, 2026
9ba8cf0
fix(threatintelligence): update the api
yoshi-automation May 19, 2026
d232bc8
feat(workstations): update the api
yoshi-automation May 19, 2026
4f41434
chore(docs): Add new discovery artifacts and artifacts with minor upd…
yoshi-automation May 19, 2026
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
The table of contents is too big for display.
Diff view
Diff view
  •  
  •  
  •  
3 changes: 3 additions & 0 deletions docs/dyn/aiplatform_v1.endpoints.html
Original file line number Diff line number Diff line change
Expand Up @@ -524,6 +524,7 @@ <h3>Method Details</h3>
},
&quot;functionDeclarations&quot;: [ # Optional. Function tool type. One or more function declarations to be passed to the model along with the current user query. Model may decide to call a subset of these functions by populating FunctionCall in the response. User should provide a FunctionResponse for each function call in the next turn. Based on the function responses, Model will generate the final response back to the user. Maximum 512 function declarations can be provided.
{ # Structured representation of a function declaration as defined by the [OpenAPI 3.0 specification](https://spec.openapis.org/oas/v3.0.3). Included in this declaration are the function name, description, parameters and response type. This FunctionDeclaration is a representation of a block of code that can be used as a `Tool` by the model and executed by the client.
&quot;behavior&quot;: &quot;A String&quot;, # Optional. Specifies the function Behavior. If not specified, the system keeps the current function call behavior. This field is currently only supported by the BidiGenerateContent method.
&quot;description&quot;: &quot;A String&quot;, # Optional. Description and purpose of the function. Model uses it to decide how and whether to call the function.
&quot;name&quot;: &quot;A String&quot;, # Required. The name of the function to call. Must start with a letter or an underscore. Must be a-z, A-Z, 0-9, or contain underscores, dots, colons and dashes, with a maximum length of 128.
&quot;parameters&quot;: { # Defines the schema of input and output data. This is a subset of the [OpenAPI 3.0 Schema Object](https://spec.openapis.org/oas/v3.0.3#schema-object). # Optional. Describes the parameters to this function in JSON Schema Object format. Reflects the Open API 3.03 Parameter Object. string Key: the name of the parameter. Parameter names are case sensitive. Schema Value: the Schema defining the type used for the parameter. For function with no parameters, this can be left unset. Parameter names must start with a letter or an underscore and must only contain chars a-z, A-Z, 0-9, or underscores with a maximum length of 64. Example with 1 required and 1 optional parameter: type: OBJECT properties: param1: type: STRING param2: type: INTEGER required: - param1
Expand Down Expand Up @@ -1108,6 +1109,7 @@ <h3>Method Details</h3>
},
&quot;functionDeclarations&quot;: [ # Optional. Function tool type. One or more function declarations to be passed to the model along with the current user query. Model may decide to call a subset of these functions by populating FunctionCall in the response. User should provide a FunctionResponse for each function call in the next turn. Based on the function responses, Model will generate the final response back to the user. Maximum 512 function declarations can be provided.
{ # Structured representation of a function declaration as defined by the [OpenAPI 3.0 specification](https://spec.openapis.org/oas/v3.0.3). Included in this declaration are the function name, description, parameters and response type. This FunctionDeclaration is a representation of a block of code that can be used as a `Tool` by the model and executed by the client.
&quot;behavior&quot;: &quot;A String&quot;, # Optional. Specifies the function Behavior. If not specified, the system keeps the current function call behavior. This field is currently only supported by the BidiGenerateContent method.
&quot;description&quot;: &quot;A String&quot;, # Optional. Description and purpose of the function. Model uses it to decide how and whether to call the function.
&quot;name&quot;: &quot;A String&quot;, # Required. The name of the function to call. Must start with a letter or an underscore. Must be a-z, A-Z, 0-9, or contain underscores, dots, colons and dashes, with a maximum length of 128.
&quot;parameters&quot;: { # Defines the schema of input and output data. This is a subset of the [OpenAPI 3.0 Schema Object](https://spec.openapis.org/oas/v3.0.3#schema-object). # Optional. Describes the parameters to this function in JSON Schema Object format. Reflects the Open API 3.03 Parameter Object. string Key: the name of the parameter. Parameter names are case sensitive. Schema Value: the Schema defining the type used for the parameter. For function with no parameters, this can be left unset. Parameter names must start with a letter or an underscore and must only contain chars a-z, A-Z, 0-9, or underscores with a maximum length of 64. Example with 1 required and 1 optional parameter: type: OBJECT properties: param1: type: STRING param2: type: INTEGER required: - param1
Expand Down Expand Up @@ -2006,6 +2008,7 @@ <h3>Method Details</h3>
},
&quot;functionDeclarations&quot;: [ # Optional. Function tool type. One or more function declarations to be passed to the model along with the current user query. Model may decide to call a subset of these functions by populating FunctionCall in the response. User should provide a FunctionResponse for each function call in the next turn. Based on the function responses, Model will generate the final response back to the user. Maximum 512 function declarations can be provided.
{ # Structured representation of a function declaration as defined by the [OpenAPI 3.0 specification](https://spec.openapis.org/oas/v3.0.3). Included in this declaration are the function name, description, parameters and response type. This FunctionDeclaration is a representation of a block of code that can be used as a `Tool` by the model and executed by the client.
&quot;behavior&quot;: &quot;A String&quot;, # Optional. Specifies the function Behavior. If not specified, the system keeps the current function call behavior. This field is currently only supported by the BidiGenerateContent method.
&quot;description&quot;: &quot;A String&quot;, # Optional. Description and purpose of the function. Model uses it to decide how and whether to call the function.
&quot;name&quot;: &quot;A String&quot;, # Required. The name of the function to call. Must start with a letter or an underscore. Must be a-z, A-Z, 0-9, or contain underscores, dots, colons and dashes, with a maximum length of 128.
&quot;parameters&quot;: { # Defines the schema of input and output data. This is a subset of the [OpenAPI 3.0 Schema Object](https://spec.openapis.org/oas/v3.0.3#schema-object). # Optional. Describes the parameters to this function in JSON Schema Object format. Reflects the Open API 3.03 Parameter Object. string Key: the name of the parameter. Parameter names are case sensitive. Schema Value: the Schema defining the type used for the parameter. For function with no parameters, this can be left unset. Parameter names must start with a letter or an underscore and must only contain chars a-z, A-Z, 0-9, or underscores with a maximum length of 64. Example with 1 required and 1 optional parameter: type: OBJECT properties: param1: type: STRING param2: type: INTEGER required: - param1
Expand Down
Loading
Loading