Skip to content

chore: Update discovery artifacts #2611

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
28 commits
Select commit Hold shift + click to select a range
b1ed08d
chore: update docs/dyn/index.md
yoshi-automation Jun 3, 2025
957e20c
feat(aiplatform): update the api
yoshi-automation Jun 3, 2025
e2b8f48
feat(alloydb): update the api
yoshi-automation Jun 3, 2025
0bdbe25
feat(androidmanagement): update the api
yoshi-automation Jun 3, 2025
a529cc6
feat(androidpublisher): update the api
yoshi-automation Jun 3, 2025
a509298
feat(chromemanagement): update the api
yoshi-automation Jun 3, 2025
0033591
feat(classroom): update the api
yoshi-automation Jun 3, 2025
c00bcab
feat(cloudresourcemanager): update the api
yoshi-automation Jun 3, 2025
c8d75a0
feat(contactcenterinsights): update the api
yoshi-automation Jun 3, 2025
d073b53
feat(datamigration): update the api
yoshi-automation Jun 3, 2025
8c45a9b
feat(dataplex): update the api
yoshi-automation Jun 3, 2025
61767d4
feat(dataproc): update the api
yoshi-automation Jun 3, 2025
b1465dc
feat(dlp): update the api
yoshi-automation Jun 3, 2025
8127a00
feat(essentialcontacts): update the api
yoshi-automation Jun 3, 2025
48e5404
feat(firebaseml): update the api
yoshi-automation Jun 3, 2025
e06fb26
feat(iap): update the api
yoshi-automation Jun 3, 2025
6327fb6
feat(networkconnectivity): update the api
yoshi-automation Jun 3, 2025
dcfaa94
feat(networkmanagement): update the api
yoshi-automation Jun 3, 2025
47e8052
feat(networksecurity): update the api
yoshi-automation Jun 3, 2025
27662ca
feat(networkservices): update the api
yoshi-automation Jun 3, 2025
733cf41
feat(retail): update the api
yoshi-automation Jun 3, 2025
b85cdbf
feat(script): update the api
yoshi-automation Jun 3, 2025
02684dc
feat(sqladmin): update the api
yoshi-automation Jun 3, 2025
3c0344e
fix(storage): update the api
yoshi-automation Jun 3, 2025
253143c
feat(vault): update the api
yoshi-automation Jun 3, 2025
cc9b1f6
feat(videointelligence): update the api
yoshi-automation Jun 3, 2025
a2ace00
feat(vmmigration): update the api
yoshi-automation Jun 3, 2025
10226a9
chore(docs): Add new discovery artifacts and artifacts with minor upd…
yoshi-automation Jun 3, 2025
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -106,7 +106,7 @@ <h3>Method Details</h3>
&quot;commandExpireTime&quot;: &quot;A String&quot;, # The time at which the command will expire. If the device doesn&#x27;t execute the command within this time the command will become expired.
&quot;commandId&quot;: &quot;A String&quot;, # Unique ID of a device command.
&quot;commandResult&quot;: { # The result of executing a command. # The result of the command execution.
&quot;commandResultPayload&quot;: &quot;A String&quot;, # The payload for the command result. The following commands respond with a payload: * `DEVICE_START_CRD_SESSION`: Payload is a stringified JSON object in the form: { &quot;url&quot;: url }. The URL provides a link to the Chrome Remote Desktop session. * `FETCH_CRD_AVAILABILITY_INFO`: Payload is a stringified JSON object in the form: { &quot;deviceIdleTimeInSeconds&quot;: number, &quot;userSessionType&quot;: string, &quot;remoteSupportAvailability&quot;: string, &quot;remoteAccessAvailability&quot;: string }. The &quot;remoteSupportAvailability&quot; field is set to &quot;AVAILABLE&quot; if `shared` CRD session to the device is available. The &quot;remoteAccessAvailability&quot; field is set to &quot;AVAILABLE&quot; if `private` CRD session to the device is available.
&quot;commandResultPayload&quot;: &quot;A String&quot;, # The payload for the command result. The following commands respond with a payload: * `DEVICE_START_CRD_SESSION`: Payload is a stringified JSON object in the form: { &quot;url&quot;: url }. The provided URL links to the Chrome Remote Desktop session and requires authentication using only the `email` associated with the command&#x27;s issuance. * `FETCH_CRD_AVAILABILITY_INFO`: Payload is a stringified JSON object in the form: { &quot;deviceIdleTimeInSeconds&quot;: number, &quot;userSessionType&quot;: string, &quot;remoteSupportAvailability&quot;: string, &quot;remoteAccessAvailability&quot;: string }. The &quot;remoteSupportAvailability&quot; field is set to &quot;AVAILABLE&quot; if `shared` CRD session to the device is available. The &quot;remoteAccessAvailability&quot; field is set to &quot;AVAILABLE&quot; if `private` CRD session to the device is available.
&quot;errorMessage&quot;: &quot;A String&quot;, # The error message with a short explanation as to why the command failed. Only present if the command failed.
&quot;executeTime&quot;: &quot;A String&quot;, # The time at which the command was executed or failed to execute.
&quot;result&quot;: &quot;A String&quot;, # The result of the command.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -151,7 +151,7 @@ <h3>Method Details</h3>

{ # A request for issuing a command.
&quot;commandType&quot;: &quot;A String&quot;, # The type of command.
&quot;payload&quot;: &quot;A String&quot;, # The payload for the command, provide it only if command supports it. The following commands support adding payload: * `SET_VOLUME`: Payload is a stringified JSON object in the form: { &quot;volume&quot;: 50 }. The volume has to be an integer in the range [0,100]. * `DEVICE_START_CRD_SESSION`: Payload is optionally a stringified JSON object in the form: { &quot;ackedUserPresence&quot;: true, &quot;crdSessionType&quot;: string }. `ackedUserPresence` is a boolean. By default, `ackedUserPresence` is set to `false`. To start a Chrome Remote Desktop session for an active device, set `ackedUserPresence` to `true`. `crdSessionType` can only select from values `private` (which grants the remote admin exclusive control of the ChromeOS device) or `shared` (which allows the admin and the local user to share control of the ChromeOS device). If not set, `crdSessionType` defaults to `shared`. * `REBOOT`: Payload is a stringified JSON object in the form: { &quot;user_session_delay_seconds&quot;: 300 }. The `user_session_delay_seconds` is the amount of seconds to wait before rebooting the device if a user is logged in. It has to be an integer in the range [0,300]. When payload is not present for reboot, 0 delay is the default. Note: This only applies if an actual user is logged in, including a Guest. If the device is in the login screen or in Kiosk mode the value is not respected and the device immediately reboots. * `FETCH_SUPPORT_PACKET`: Payload is optionally a stringified JSON object in the form: {&quot;supportPacketDetails&quot;:{ &quot;issueCaseId&quot;: optional_support_case_id_string, &quot;issueDescription&quot;: optional_issue_description_string, &quot;requestedDataCollectors&quot;: []}} The list of available `data_collector_enums` are as following: Chrome System Information (1), Crash IDs (2), Memory Details (3), UI Hierarchy (4), Additional ChromeOS Platform Logs (5), Device Event (6), Intel WiFi NICs Debug Dump (7), Touch Events (8), Lacros (9), Lacros System Information (10), ChromeOS Flex Logs (11), DBus Details (12), ChromeOS Network Routes (13), ChromeOS Shill (Connection Manager) Logs (14), Policies (15), ChromeOS System State and Logs (16), ChromeOS System Logs (17), ChromeOS Chrome User Logs (18), ChromeOS Bluetooth (19), ChromeOS Connected Input Devices (20), ChromeOS Traffic Counters (21), ChromeOS Virtual Keyboard (22), ChromeOS Network Health (23). See more details in [help article](https://support.google.com/chrome/a?p=remote-log).
&quot;payload&quot;: &quot;A String&quot;, # The payload for the command, provide it only if command supports it. The following commands support adding payload: * `SET_VOLUME`: Payload is a stringified JSON object in the form: { &quot;volume&quot;: 50 }. The volume has to be an integer in the range [0,100]. * `DEVICE_START_CRD_SESSION`: Payload is optionally a stringified JSON object in the form: { &quot;ackedUserPresence&quot;: true, &quot;crdSessionType&quot;: string }. `ackedUserPresence` is a boolean. By default, `ackedUserPresence` is set to `false`. To start a Chrome Remote Desktop session for an active device, set `ackedUserPresence` to `true`. `crdSessionType` can only select from values `private` (which grants the remote admin exclusive control of the ChromeOS device) or `shared` (which allows the admin and the local user to share control of the ChromeOS device). If not set, `crdSessionType` defaults to `shared`. The `FETCH_CRD_AVAILABILITY_INFO` command can be used to determine available session types on the device. * `REBOOT`: Payload is a stringified JSON object in the form: { &quot;user_session_delay_seconds&quot;: 300 }. The `user_session_delay_seconds` is the amount of seconds to wait before rebooting the device if a user is logged in. It has to be an integer in the range [0,300]. When payload is not present for reboot, 0 delay is the default. Note: This only applies if an actual user is logged in, including a Guest. If the device is in the login screen or in Kiosk mode the value is not respected and the device immediately reboots. * `FETCH_SUPPORT_PACKET`: Payload is optionally a stringified JSON object in the form: {&quot;supportPacketDetails&quot;:{ &quot;issueCaseId&quot;: optional_support_case_id_string, &quot;issueDescription&quot;: optional_issue_description_string, &quot;requestedDataCollectors&quot;: []}} The list of available `data_collector_enums` are as following: Chrome System Information (1), Crash IDs (2), Memory Details (3), UI Hierarchy (4), Additional ChromeOS Platform Logs (5), Device Event (6), Intel WiFi NICs Debug Dump (7), Touch Events (8), Lacros (9), Lacros System Information (10), ChromeOS Flex Logs (11), DBus Details (12), ChromeOS Network Routes (13), ChromeOS Shill (Connection Manager) Logs (14), Policies (15), ChromeOS System State and Logs (16), ChromeOS System Logs (17), ChromeOS Chrome User Logs (18), ChromeOS Bluetooth (19), ChromeOS Connected Input Devices (20), ChromeOS Traffic Counters (21), ChromeOS Virtual Keyboard (22), ChromeOS Network Health (23). See more details in [help article](https://support.google.com/chrome/a?p=remote-log).
}

x__xgafv: string, V1 error format.
Expand Down
Loading