You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I haven't been able to find any references in the documentation to Drive integration. The quickstart documentation still references the google-api-python-client library, which is in maintenance mode and promotes migration to this library.
Does anybody have any insight on how best to integrate with this library? My primary motivations for using this library is to use this on a Lambda. The promise of a smaller package size compared to ~>50mb size of the google-api-python-client bloat since 2.0.2 due to the inclusion of the discovery_cache documents is making it impossible to deploy.
The text was updated successfully, but these errors were encountered:
A request has been filed with the Team that maintains the Drive Activity API, as this API already has public protobuf files. Googlers See b/315538073.
If there are specific Drive APIs where you would like to see client libraries, please let us know so we can reach out to the teams internally. Alternatively, you can click the Send Feedback or Submit feature request button in the support section of any given API to reach the API team directly and request client libraries. For example, this page for the Drive API has both the Send Feedback and Submit feature request buttons.
I haven't been able to find any references in the documentation to Drive integration. The quickstart documentation still references the google-api-python-client library, which is in maintenance mode and promotes migration to this library.
Does anybody have any insight on how best to integrate with this library? My primary motivations for using this library is to use this on a Lambda. The promise of a smaller package size compared to ~>50mb size of the google-api-python-client bloat since 2.0.2 due to the inclusion of the discovery_cache documents is making it impossible to deploy.
The text was updated successfully, but these errors were encountered: