Skip to content
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

feat: run the generator #3552

Open
wants to merge 83 commits into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
83 commits
Select commit Hold shift + click to select a range
506adff
feat(accesscontextmanager): update the API
yoshi-automation Sep 21, 2024
9c2bd60
fix(admin): update the API
yoshi-automation Sep 21, 2024
f874f02
feat(aiplatform): update the API
yoshi-automation Sep 21, 2024
494bd44
feat(alloydb): update the API
yoshi-automation Sep 21, 2024
da8e23f
fix(analyticsadmin): update the API
yoshi-automation Sep 21, 2024
2c67ae3
feat(androiddeviceprovisioning): update the API
yoshi-automation Sep 21, 2024
ed3a891
feat(androidmanagement): update the API
yoshi-automation Sep 21, 2024
7d9a3ff
fix(androidpublisher): update the API
yoshi-automation Sep 21, 2024
30d7ecd
feat(appengine): update the API
yoshi-automation Sep 21, 2024
26bd6df
feat(artifactregistry): update the API
yoshi-automation Sep 21, 2024
25d1b6b
feat(backupdr): update the API
yoshi-automation Sep 21, 2024
ab94836
fix(batch): update the API
yoshi-automation Sep 21, 2024
6b68727
feat(beyondcorp)!: update the API
yoshi-automation Sep 21, 2024
2c3fd6c
fix(bigquery): update the API
yoshi-automation Sep 21, 2024
e26e3e4
feat(bigquerydatatransfer): update the API
yoshi-automation Sep 21, 2024
bd326ec
feat(bigtableadmin): update the API
yoshi-automation Sep 21, 2024
8110d0b
fix(calendar): update the API
yoshi-automation Sep 21, 2024
9de047b
feat(chat): update the API
yoshi-automation Sep 21, 2024
2832a08
feat(checks): update the API
yoshi-automation Sep 21, 2024
6a06baf
feat(chromeuxreport)!: update the API
yoshi-automation Sep 21, 2024
8824ff7
feat(civicinfo): update the API
yoshi-automation Sep 21, 2024
182c306
fix(classroom): update the API
yoshi-automation Sep 21, 2024
fe04dba
fix(cloudbilling): update the API
yoshi-automation Sep 21, 2024
6d2fc6b
fix(cloudbuild): update the API
yoshi-automation Sep 21, 2024
b1f4141
feat(cloudchannel)!: update the API
yoshi-automation Sep 21, 2024
ec61554
fix(cloudcontrolspartner): update the API
yoshi-automation Sep 21, 2024
0e4f7bf
feat(cloudfunctions)!: update the API
yoshi-automation Sep 21, 2024
694941b
feat(compute): update the API
yoshi-automation Sep 21, 2024
6df9a0c
feat(connectors): update the API
yoshi-automation Sep 21, 2024
60229e1
feat(contactcenteraiplatform): update the API
yoshi-automation Sep 21, 2024
482cf6b
feat(contactcenterinsights): update the API
yoshi-automation Sep 21, 2024
b380afd
feat(container): update the API
yoshi-automation Sep 21, 2024
fcbd005
feat(containeranalysis): update the API
yoshi-automation Sep 21, 2024
23d02ff
feat(css): update the API
yoshi-automation Sep 21, 2024
fdc2bfa
feat(datamigration): update the API
yoshi-automation Sep 21, 2024
b21c6a1
feat(dataplex)!: update the API
yoshi-automation Sep 21, 2024
0a5c455
feat(datastream): update the API
yoshi-automation Sep 21, 2024
e256972
fix(dialogflow): update the API
yoshi-automation Sep 21, 2024
8ee9ece
feat(discoveryengine)!: update the API
yoshi-automation Sep 21, 2024
526c588
fix(displayvideo): update the API
yoshi-automation Sep 21, 2024
fff5b5c
feat(dlp): update the API
yoshi-automation Sep 21, 2024
7e45cc1
feat(documentai)!: update the API
yoshi-automation Sep 21, 2024
0135a51
feat(drive): update the API
yoshi-automation Sep 21, 2024
6ac748e
feat(eventarc): update the API
yoshi-automation Sep 21, 2024
35e61a5
feat(file): update the API
yoshi-automation Sep 21, 2024
843e4a2
feat(firebase): update the API
yoshi-automation Sep 21, 2024
98bbcf7
feat(firebaseml): update the API
yoshi-automation Sep 21, 2024
85423c7
feat(firestore): update the API
yoshi-automation Sep 21, 2024
4ee518d
feat(gkehub): update the API
yoshi-automation Sep 21, 2024
90c8d1d
feat(healthcare): update the API
yoshi-automation Sep 21, 2024
fe7f6d3
fix(iap): update the API
yoshi-automation Sep 21, 2024
5285f59
feat(logging): update the API
yoshi-automation Sep 21, 2024
9955fd0
feat(looker): update the API
yoshi-automation Sep 21, 2024
b47925d
feat(merchantapi)!: update the API
yoshi-automation Sep 21, 2024
281097a
feat(migrationcenter)!: update the API
yoshi-automation Sep 21, 2024
ea4c6f0
feat(monitoring): update the API
yoshi-automation Sep 21, 2024
2f1f931
feat(networkconnectivity): update the API
yoshi-automation Sep 21, 2024
96c4cc3
feat(networkmanagement): update the API
yoshi-automation Sep 21, 2024
1556a53
feat(networksecurity): update the API
yoshi-automation Sep 21, 2024
5971de1
feat(networkservices): update the API
yoshi-automation Sep 21, 2024
f9456d0
fix(oracledatabase): update the API
yoshi-automation Sep 21, 2024
b9de0be
feat(places): update the API
yoshi-automation Sep 21, 2024
a92bcae
fix(pubsub): update the API
yoshi-automation Sep 21, 2024
4b9b9c1
fix(recaptchaenterprise): update the API
yoshi-automation Sep 21, 2024
19c0407
feat(redis): update the API
yoshi-automation Sep 21, 2024
b6f7e79
feat(retail): update the API
yoshi-automation Sep 21, 2024
cbb0f80
feat(run): update the API
yoshi-automation Sep 21, 2024
64361ca
feat(securitycenter): update the API
yoshi-automation Sep 21, 2024
fa13104
feat(serviceconsumermanagement): update the API
yoshi-automation Sep 21, 2024
294d7f8
feat(servicenetworking): update the API
yoshi-automation Sep 21, 2024
5aae881
feat(serviceusage): update the API
yoshi-automation Sep 21, 2024
bd6bba3
feat(sqladmin): update the API
yoshi-automation Sep 21, 2024
cd61fba
feat(storage): update the API
yoshi-automation Sep 21, 2024
1365dc6
fix(sts): update the API
yoshi-automation Sep 21, 2024
05fd77c
feat(testing): update the API
yoshi-automation Sep 21, 2024
ed3f606
feat(tpu): update the API
yoshi-automation Sep 21, 2024
a24fae4
fix(vision): update the API
yoshi-automation Sep 21, 2024
85dcf96
fix(vmmigration): update the API
yoshi-automation Sep 21, 2024
158f701
feat(vpcaccess): update the API
yoshi-automation Sep 21, 2024
24b70ec
fix(workstations): update the API
yoshi-automation Sep 21, 2024
1720571
feat(youtube): update the API
yoshi-automation Sep 21, 2024
cc62039
feat: regenerate index files
yoshi-automation Sep 21, 2024
be4ea91
🦉 Updates from OwlBot post-processor
gcf-owl-bot[bot] Sep 21, 2024
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
113 changes: 112 additions & 1 deletion discovery/accesscontextmanager-v1.json
Original file line number Diff line number Diff line change
Expand Up @@ -1290,7 +1290,7 @@
}
}
},
"revision": "20240811",
"revision": "20240908",
"rootUrl": "https://accesscontextmanager.googleapis.com/",
"schemas": {
"AccessContextManagerOperationMetadata": {
Expand Down Expand Up @@ -1357,6 +1357,35 @@
},
"type": "object"
},
"AccessScope": {
"description": "Access scope represents the client scope, etc. to which the settings will be applied to.",
"id": "AccessScope",
"properties": {
"clientScope": {
"$ref": "ClientScope",
"description": "Optional. Client scope for this access scope."
}
},
"type": "object"
},
"AccessSettings": {
"description": "Access settings represent the set of conditions that must be met for access to be granted. At least one of the fields must be set.",
"id": "AccessSettings",
"properties": {
"accessLevels": {
"description": "Optional. Access level that a user must have to be granted access. Only one access level is supported, not multiple. This repeated field must have exactly one element. Example: \"accessPolicies/9522/accessLevels/device_trusted\"",
"items": {
"type": "string"
},
"type": "array"
},
"reauthSettings": {
"$ref": "ReauthSettings",
"description": "Optional. Reauth settings applied to user access on a given AccessScope."
}
},
"type": "object"
},
"ApiOperation": {
"description": "Identification for an API Operation.",
"id": "ApiOperation",
Expand Down Expand Up @@ -1550,6 +1579,17 @@
"properties": {},
"type": "object"
},
"ClientScope": {
"description": "Client scope represents the application, etc. subject to this binding's restrictions.",
"id": "ClientScope",
"properties": {
"restrictedClientApplication": {
"$ref": "Application",
"description": "Optional. The application that is subject to this binding's scope."
}
},
"type": "object"
},
"CommitServicePerimetersRequest": {
"description": "A request to commit dry-run specs in all Service Perimeters belonging to an Access Policy.",
"id": "CommitServicePerimetersRequest",
Expand Down Expand Up @@ -1860,12 +1900,23 @@
"description": "Immutable. Assigned by the server during creation. The last segment has an arbitrary length and has only URI unreserved characters (as defined by [RFC 3986 Section 2.3](https://tools.ietf.org/html/rfc3986#section-2.3)). Should not be specified by the client during creation. Example: \"organizations/256/gcpUserAccessBindings/b3-BhcX_Ud5N\"",
"type": "string"
},
"reauthSettings": {
"$ref": "ReauthSettings",
"description": "Optional. GCSL policy for the group key."
},
"restrictedClientApplications": {
"description": "Optional. A list of applications that are subject to this binding's restrictions. If the list is empty, the binding restrictions will universally apply to all applications.",
"items": {
"$ref": "Application"
},
"type": "array"
},
"scopedAccessSettings": {
"description": "Optional. A list of scoped access settings that set this binding's restrictions on a subset of applications. This field cannot be set if restricted_client_applications is set.",
"items": {
"$ref": "ScopedAccessSettings"
},
"type": "array"
}
},
"type": "object"
Expand Down Expand Up @@ -2231,6 +2282,47 @@
},
"type": "object"
},
"ReauthSettings": {
"description": "Stores settings related to Google Cloud Session Length including session duration, the type of challenge (i.e. method) they should face when their session expires, and other related settings.",
"id": "ReauthSettings",
"properties": {
"maxInactivity": {
"description": "Optional. How long a user is allowed to take between actions before a new access token must be issued. Presently only set for Cloud Apps.",
"format": "google-duration",
"type": "string"
},
"reauthMethod": {
"description": "Optional. Reauth method when users GCP session is up.",
"enum": [
"REAUTH_METHOD_UNSPECIFIED",
"LOGIN",
"SECURITY_KEY",
"PASSWORD"
],
"enumDescriptions": [
"If method undefined in API, we will use LOGIN by default.",
"The user will prompted to perform regular login. Users who are enrolled for two-step verification and haven't chosen to \"Remember this computer\" will be prompted for their second factor.",
"The user will be prompted to autheticate using their security key. If no security key has been configured, then we will fallback to LOGIN.",
"The user will be prompted for their password."
],
"type": "string"
},
"sessionLength": {
"description": "Optional. The session length. Setting this field to zero is equal to disabling. Reauth. Also can set infinite session by flipping the enabled bit to false below. If use_oidc_max_age is true, for OIDC apps, the session length will be the minimum of this field and OIDC max_age param.",
"format": "google-duration",
"type": "string"
},
"sessionLengthEnabled": {
"description": "Optional. Big red button to turn off GCSL. When false, all fields set above will be disregarded and the session length is basically infinite.",
"type": "boolean"
},
"useOidcMaxAge": {
"description": "Optional. Only useful for OIDC apps. When false, the OIDC max_age param, if passed in the authentication request will be ignored. When true, the re-auth period will be the minimum of the session_length field and the max_age OIDC param.",
"type": "boolean"
}
},
"type": "object"
},
"ReplaceAccessLevelsRequest": {
"description": "A request to replace all existing Access Levels in an Access Policy with the Access Levels provided. This is done atomically.",
"id": "ReplaceAccessLevelsRequest",
Expand Down Expand Up @@ -2295,6 +2387,25 @@
},
"type": "object"
},
"ScopedAccessSettings": {
"description": "A relationship between access settings and its scope.",
"id": "ScopedAccessSettings",
"properties": {
"activeSettings": {
"$ref": "AccessSettings",
"description": "Optional. Access settings for this scoped access settings. This field may be empty if dry_run_settings is set."
},
"dryRunSettings": {
"$ref": "AccessSettings",
"description": "Optional. Dry-run access settings for this scoped access settings. This field may be empty if active_settings is set."
},
"scope": {
"$ref": "AccessScope",
"description": "Optional. Application, etc. to which the access settings will be applied to. Implicitly, this is the scoped access settings key; as such, it must be unique and non-empty."
}
},
"type": "object"
},
"ServicePerimeter": {
"description": "`ServicePerimeter` describes a set of Google Cloud resources which can freely import and export data amongst themselves, but not export outside of the `ServicePerimeter`. If a request with a source within this `ServicePerimeter` has a target outside of the `ServicePerimeter`, the request will be blocked. Otherwise the request is allowed. There are two types of Service Perimeter - Regular and Bridge. Regular Service Perimeters cannot overlap, a single Google Cloud project or VPC network can only belong to a single regular Service Perimeter. Service Perimeter Bridges can contain only Google Cloud projects as members, a single Google Cloud project may belong to multiple Service Perimeter Bridges.",
"id": "ServicePerimeter",
Expand Down
6 changes: 3 additions & 3 deletions discovery/admin-directory_v1.json
Original file line number Diff line number Diff line change
Expand Up @@ -1677,7 +1677,7 @@
"type": "string"
},
"userKey": {
"description": "Email or immutable ID of the user if only those groups are to be listed, the given user is a member of. If it's an ID, it should match with the ID of the user object.",
"description": "Email or immutable ID of the user if only those groups are to be listed, the given user is a member of. If it's an ID, it should match with the ID of the user object. Cannot be used with the `customer` parameter.",
"location": "query",
"type": "string"
}
Expand Down Expand Up @@ -4671,7 +4671,7 @@
}
}
},
"revision": "20240709",
"revision": "20240917",
"rootUrl": "https://admin.googleapis.com/",
"schemas": {
"Alias": {
Expand Down Expand Up @@ -6245,7 +6245,7 @@
"type": "string"
},
"payload": {
"description": "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: { \"volume\": 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: { \"ackedUserPresence\": true }. `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`. * `REBOOT`: Payload is a stringified JSON object in the form: { \"user_session_delay_seconds\": 300 }. The delay has to be in the range [0, 300]. * `FETCH_SUPPORT_PACKET`: Payload is optionally a stringified JSON object in the form: {\"supportPacketDetails\":{ \"issueCaseId\": optional_support_case_id_string, \"issueDescription\": optional_issue_description_string, \"requestedDataCollectors\": []}} 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).",
"description": "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: { \"volume\": 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: { \"ackedUserPresence\": true, \"crdSessionType\": 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: { \"user_session_delay_seconds\": 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: {\"supportPacketDetails\":{ \"issueCaseId\": optional_support_case_id_string, \"issueDescription\": optional_issue_description_string, \"requestedDataCollectors\": []}} 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).",
"type": "string"
}
},
Expand Down
Loading