Skip to content

chore: Update discovery artifacts #1814

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.

Sign up for GitHub

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
merged 19 commits into from
May 31, 2022
Merged

chore: Update discovery artifacts #1814

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
19 commits
Select commit Hold shift + click to select a range
12c0c71
chore: update docs/dyn/index.md
yoshi-automation May 31, 2022
1e8afff
feat(androidmanagement): update the api
yoshi-automation May 31, 2022
0f73a4a
feat(apigee): update the api
yoshi-automation May 31, 2022
355e7c6
feat(baremetalsolution): update the api
yoshi-automation May 31, 2022
9443852
feat(cloudidentity): update the api
yoshi-automation May 31, 2022
324fcf1
feat(cloudresourcemanager): update the api
yoshi-automation May 31, 2022
2bf29de
feat(cloudsearch): update the api
yoshi-automation May 31, 2022
40b5fd6
feat(compute): update the api
yoshi-automation May 31, 2022
e2c58b5
feat(containeranalysis): update the api
yoshi-automation May 31, 2022
4592dcb
feat(dataproc): update the api
yoshi-automation May 31, 2022
a534b6a
feat(dialogflow): update the api
yoshi-automation May 31, 2022
2d529a8
feat(displayvideo): update the api
yoshi-automation May 31, 2022
8f554cc
feat(ondemandscanning): update the api
yoshi-automation May 31, 2022
122a226
feat(recaptchaenterprise): update the api
yoshi-automation May 31, 2022
130c317
feat(securitycenter): update the api
yoshi-automation May 31, 2022
5dbe3b6
feat(servicemanagement): update the api
yoshi-automation May 31, 2022
d207c0d
feat(servicenetworking): update the api
yoshi-automation May 31, 2022
82a4625
feat(vmmigration): update the api
yoshi-automation May 31, 2022
bd72784
chore(docs): Add new discovery artifacts and artifacts with minor upd…
yoshi-automation May 31, 2022
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
  •  
  •  
  •  
52 changes: 52 additions & 0 deletions docs/dyn/androidmanagement_v1.enterprises.devices.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -192,6 +192,7 @@ <h3>Method Details</h3>
&quot;passwordQuality&quot;: &quot;A String&quot;, # The required password quality.
&quot;passwordScope&quot;: &quot;A String&quot;, # The scope that the password requirement applies to.
&quot;requirePasswordUnlock&quot;: &quot;A String&quot;, # The length of time after a device or work profile is unlocked using a strong form of authentication (password, PIN, pattern) that it can be unlocked using any other authentication method (e.g. fingerprint, trust agents, face). After the specified time period elapses, only strong forms of authentication can be used to unlock the device or work profile.
&quot;unifiedLockSettings&quot;: &quot;A String&quot;, # Controls whether a unified lock is allowed for the device and the work profile, on devices running Android 9 and above with a work profile. This can be set only if password_scope is set to SCOPE_PROFILE, the policy will be rejected otherwise. If user has not set a separate work lock and this field is set to REQUIRE_SEPARATE_WORK_LOCK, a NonComplianceDetail is reported with nonComplianceReason set to USER_ACTION.
},
],
&quot;appliedPolicyName&quot;: &quot;A String&quot;, # The name of the policy currently applied to the device.
Expand Down Expand Up @@ -321,6 +322,15 @@ <h3>Method Details</h3>
&quot;nonComplianceReason&quot;: &quot;A String&quot;, # The reason the device is not in compliance with the setting.
&quot;packageName&quot;: &quot;A String&quot;, # The package name indicating which app is out of compliance, if applicable.
&quot;settingName&quot;: &quot;A String&quot;, # The name of the policy setting. This is the JSON field name of a top-level Policy field.
&quot;specificNonComplianceContext&quot;: { # Additional context for SpecificNonComplianceReason. # Additional context for specific_non_compliance_reason.
&quot;oncWifiContext&quot;: { # Additional context for non-compliance related to Wi-Fi configuration. # Additional context for non-compliance related to Wi-Fi configuration. See ONC_WIFI_INVALID_VALUE.
&quot;wifiGuid&quot;: &quot;A String&quot;, # The guid of non-compliant Wi-Fi configuration.
},
&quot;passwordPoliciesContext&quot;: { # Additional context for non-compliance related to password policies. # Additional context for non-compliance related to password policies. See PASSWORD_POLICIES_PASSWORD_EXPIRED, and PASSWORD_POLICIES_PASSWORD_NOT_SUFFICIENT.
&quot;passwordPolicyScope&quot;: &quot;A String&quot;, # The scope of non-compliant password.
},
},
&quot;specificNonComplianceReason&quot;: &quot;A String&quot;, # The policy-specific reason the device is not in compliance with the setting.
},
],
&quot;ownership&quot;: &quot;A String&quot;, # Ownership of the managed device.
Expand Down Expand Up @@ -389,6 +399,18 @@ <h3>Method Details</h3>
The object takes the form of:

{ # A command.
&quot;clearAppsDataParams&quot;: { # Parameters associated with the CLEAR_APP_DATA command to clear the data of specified apps from the device. # Parameters for the CLEAR_APP_DATA command to clear the data of specified apps from the device. See ClearAppsDataParams. If this is set, then it is suggested that type should not be set. In this case, the server automatically sets it to CLEAR_APP_DATA. It is also acceptable to explicitly set type to CLEAR_APP_DATA.
&quot;packageNames&quot;: [ # The package names of the apps whose data will be cleared when the command is executed.
&quot;A String&quot;,
],
},
&quot;clearAppsDataStatus&quot;: { # Status of the CLEAR_APP_DATA command to clear the data of specified apps from the device. # Output only. Status of the CLEAR_APP_DATA command to clear the data of specified apps from the device. See ClearAppsDataStatus.
&quot;results&quot;: { # The per-app results, a mapping from package names to the respective clearing result.
&quot;a_key&quot;: { # The result of an attempt to clear the data of a single app.
&quot;clearingResult&quot;: &quot;A String&quot;, # The result of an attempt to clear the data of a single app.
},
},
},
&quot;createTime&quot;: &quot;A String&quot;, # The timestamp at which the command was created. The timestamp is automatically generated by the server.
&quot;duration&quot;: &quot;A String&quot;, # The duration for which the command is valid. The command will expire if not executed by the device during this time. The default duration if unspecified is ten minutes. There is no maximum duration.
&quot;errorCode&quot;: &quot;A String&quot;, # If the command failed, an error code explaining the failure. This is not set when the command is cancelled by the caller.
Expand Down Expand Up @@ -495,6 +517,7 @@ <h3>Method Details</h3>
&quot;passwordQuality&quot;: &quot;A String&quot;, # The required password quality.
&quot;passwordScope&quot;: &quot;A String&quot;, # The scope that the password requirement applies to.
&quot;requirePasswordUnlock&quot;: &quot;A String&quot;, # The length of time after a device or work profile is unlocked using a strong form of authentication (password, PIN, pattern) that it can be unlocked using any other authentication method (e.g. fingerprint, trust agents, face). After the specified time period elapses, only strong forms of authentication can be used to unlock the device or work profile.
&quot;unifiedLockSettings&quot;: &quot;A String&quot;, # Controls whether a unified lock is allowed for the device and the work profile, on devices running Android 9 and above with a work profile. This can be set only if password_scope is set to SCOPE_PROFILE, the policy will be rejected otherwise. If user has not set a separate work lock and this field is set to REQUIRE_SEPARATE_WORK_LOCK, a NonComplianceDetail is reported with nonComplianceReason set to USER_ACTION.
},
],
&quot;appliedPolicyName&quot;: &quot;A String&quot;, # The name of the policy currently applied to the device.
Expand Down Expand Up @@ -624,6 +647,15 @@ <h3>Method Details</h3>
&quot;nonComplianceReason&quot;: &quot;A String&quot;, # The reason the device is not in compliance with the setting.
&quot;packageName&quot;: &quot;A String&quot;, # The package name indicating which app is out of compliance, if applicable.
&quot;settingName&quot;: &quot;A String&quot;, # The name of the policy setting. This is the JSON field name of a top-level Policy field.
&quot;specificNonComplianceContext&quot;: { # Additional context for SpecificNonComplianceReason. # Additional context for specific_non_compliance_reason.
&quot;oncWifiContext&quot;: { # Additional context for non-compliance related to Wi-Fi configuration. # Additional context for non-compliance related to Wi-Fi configuration. See ONC_WIFI_INVALID_VALUE.
&quot;wifiGuid&quot;: &quot;A String&quot;, # The guid of non-compliant Wi-Fi configuration.
},
&quot;passwordPoliciesContext&quot;: { # Additional context for non-compliance related to password policies. # Additional context for non-compliance related to password policies. See PASSWORD_POLICIES_PASSWORD_EXPIRED, and PASSWORD_POLICIES_PASSWORD_NOT_SUFFICIENT.
&quot;passwordPolicyScope&quot;: &quot;A String&quot;, # The scope of non-compliant password.
},
},
&quot;specificNonComplianceReason&quot;: &quot;A String&quot;, # The policy-specific reason the device is not in compliance with the setting.
},
],
&quot;ownership&quot;: &quot;A String&quot;, # Ownership of the managed device.
Expand Down Expand Up @@ -756,6 +788,7 @@ <h3>Method Details</h3>
&quot;passwordQuality&quot;: &quot;A String&quot;, # The required password quality.
&quot;passwordScope&quot;: &quot;A String&quot;, # The scope that the password requirement applies to.
&quot;requirePasswordUnlock&quot;: &quot;A String&quot;, # The length of time after a device or work profile is unlocked using a strong form of authentication (password, PIN, pattern) that it can be unlocked using any other authentication method (e.g. fingerprint, trust agents, face). After the specified time period elapses, only strong forms of authentication can be used to unlock the device or work profile.
&quot;unifiedLockSettings&quot;: &quot;A String&quot;, # Controls whether a unified lock is allowed for the device and the work profile, on devices running Android 9 and above with a work profile. This can be set only if password_scope is set to SCOPE_PROFILE, the policy will be rejected otherwise. If user has not set a separate work lock and this field is set to REQUIRE_SEPARATE_WORK_LOCK, a NonComplianceDetail is reported with nonComplianceReason set to USER_ACTION.
},
],
&quot;appliedPolicyName&quot;: &quot;A String&quot;, # The name of the policy currently applied to the device.
Expand Down Expand Up @@ -885,6 +918,15 @@ <h3>Method Details</h3>
&quot;nonComplianceReason&quot;: &quot;A String&quot;, # The reason the device is not in compliance with the setting.
&quot;packageName&quot;: &quot;A String&quot;, # The package name indicating which app is out of compliance, if applicable.
&quot;settingName&quot;: &quot;A String&quot;, # The name of the policy setting. This is the JSON field name of a top-level Policy field.
&quot;specificNonComplianceContext&quot;: { # Additional context for SpecificNonComplianceReason. # Additional context for specific_non_compliance_reason.
&quot;oncWifiContext&quot;: { # Additional context for non-compliance related to Wi-Fi configuration. # Additional context for non-compliance related to Wi-Fi configuration. See ONC_WIFI_INVALID_VALUE.
&quot;wifiGuid&quot;: &quot;A String&quot;, # The guid of non-compliant Wi-Fi configuration.
},
&quot;passwordPoliciesContext&quot;: { # Additional context for non-compliance related to password policies. # Additional context for non-compliance related to password policies. See PASSWORD_POLICIES_PASSWORD_EXPIRED, and PASSWORD_POLICIES_PASSWORD_NOT_SUFFICIENT.
&quot;passwordPolicyScope&quot;: &quot;A String&quot;, # The scope of non-compliant password.
},
},
&quot;specificNonComplianceReason&quot;: &quot;A String&quot;, # The policy-specific reason the device is not in compliance with the setting.
},
],
&quot;ownership&quot;: &quot;A String&quot;, # Ownership of the managed device.
Expand Down Expand Up @@ -999,6 +1041,7 @@ <h3>Method Details</h3>
&quot;passwordQuality&quot;: &quot;A String&quot;, # The required password quality.
&quot;passwordScope&quot;: &quot;A String&quot;, # The scope that the password requirement applies to.
&quot;requirePasswordUnlock&quot;: &quot;A String&quot;, # The length of time after a device or work profile is unlocked using a strong form of authentication (password, PIN, pattern) that it can be unlocked using any other authentication method (e.g. fingerprint, trust agents, face). After the specified time period elapses, only strong forms of authentication can be used to unlock the device or work profile.
&quot;unifiedLockSettings&quot;: &quot;A String&quot;, # Controls whether a unified lock is allowed for the device and the work profile, on devices running Android 9 and above with a work profile. This can be set only if password_scope is set to SCOPE_PROFILE, the policy will be rejected otherwise. If user has not set a separate work lock and this field is set to REQUIRE_SEPARATE_WORK_LOCK, a NonComplianceDetail is reported with nonComplianceReason set to USER_ACTION.
},
],
&quot;appliedPolicyName&quot;: &quot;A String&quot;, # The name of the policy currently applied to the device.
Expand Down Expand Up @@ -1128,6 +1171,15 @@ <h3>Method Details</h3>
&quot;nonComplianceReason&quot;: &quot;A String&quot;, # The reason the device is not in compliance with the setting.
&quot;packageName&quot;: &quot;A String&quot;, # The package name indicating which app is out of compliance, if applicable.
&quot;settingName&quot;: &quot;A String&quot;, # The name of the policy setting. This is the JSON field name of a top-level Policy field.
&quot;specificNonComplianceContext&quot;: { # Additional context for SpecificNonComplianceReason. # Additional context for specific_non_compliance_reason.
&quot;oncWifiContext&quot;: { # Additional context for non-compliance related to Wi-Fi configuration. # Additional context for non-compliance related to Wi-Fi configuration. See ONC_WIFI_INVALID_VALUE.
&quot;wifiGuid&quot;: &quot;A String&quot;, # The guid of non-compliant Wi-Fi configuration.
},
&quot;passwordPoliciesContext&quot;: { # Additional context for non-compliance related to password policies. # Additional context for non-compliance related to password policies. See PASSWORD_POLICIES_PASSWORD_EXPIRED, and PASSWORD_POLICIES_PASSWORD_NOT_SUFFICIENT.
&quot;passwordPolicyScope&quot;: &quot;A String&quot;, # The scope of non-compliant password.
},
},
&quot;specificNonComplianceReason&quot;: &quot;A String&quot;, # The policy-specific reason the device is not in compliance with the setting.
},
],
&quot;ownership&quot;: &quot;A String&quot;, # Ownership of the managed device.
Expand Down
Loading