chiu
/
google-api-ruby-client
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

chore: Update some language prior to releasing separated clients

This commit is contained in:
Daniel Azuma 2021-01-07 14:57:10 -08:00 committed by GitHub
parent 2c145d4206
commit ff33830fa8
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1204 changed files with 4916 additions and 4917 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/auth-guide.md
View File

@ -1,8 +1,8 @@
# Authentication for Legacy REST Clients
# Authentication for Simple REST Clients
This document describes how authentication, authorization, and accounting are accomplished. For all API calls, your application needs to be authenticated. When an API accesses a user's private data, your application must also be authorized by the user to access the data. For example, accessing a public Google+ post would not require user authorization, but accessing a user's private calendar would. Also, for quota and billing purposes, all API calls involve accounting. This document summarizes the protocols used by Google APIs and provides links to more information.
> **Note:** this is a "general" document, and not specific to this particular service client. In particular, you may find that the examples in this document are for a different client. All legacy REST clients follow the same usage patterns, and you should be able to adapt the provided examples to the client you are using.
> **Note:** this is a "general" document, and not specific to this particular service client. In particular, you may find that the examples in this document are for a different client. All simple REST clients follow the same usage patterns, and you should be able to adapt the provided examples to the client you are using.
## Access types

2
docs/oauth-installed.md
View File

@ -11,7 +11,7 @@ If you are writing an app for Android or iOS, use [Google Sign-In](https://devel
If your app will run on devices that do not have access to a system browser, or devices with limited input capabilities (for example, if your app will run on game consoles, video cameras, or printers), then see [Using OAuth 2.0 for Devices](https://developers.google.com/accounts/docs/OAuth2ForDevices).
> **Note:** this is a "general" document, and not specific to this particular service client. In particular, you may find that the examples in this document are for a different client. All legacy REST clients follow the same usage patterns, and you should be able to adapt the provided examples to the client you are using.
> **Note:** this is a "general" document, and not specific to this particular service client. In particular, you may find that the examples in this document are for a different client. All simple REST clients follow the same usage patterns, and you should be able to adapt the provided examples to the client you are using.
## Overview

2
docs/oauth-server.md
View File

@ -12,7 +12,7 @@ If you have a G Suite domain—if you use [G Suite](https://gsuite.google.com/),
This document describes how an application can complete the server-to-server OAuth 2.0 flow by using the Google APIs Client Library for Ruby.
> **Note:** this is a "general" document, and not specific to this particular service client. In particular, you may find that the examples in this document are for a different client. All legacy REST clients follow the same usage patterns, and you should be able to adapt the provided examples to the client you are using.
> **Note:** this is a "general" document, and not specific to this particular service client. In particular, you may find that the examples in this document are for a different client. All simple REST clients follow the same usage patterns, and you should be able to adapt the provided examples to the client you are using.
## Overview

2
docs/oauth-web.md
View File

@ -6,7 +6,7 @@ This OAuth 2.0 flow is specifically for user authorization. It is designed for a
Web server applications frequently also use service accounts to authorize API requests, particularly when calling Cloud APIs to access project-based data rather than user-specific data. Web server applications can use service accounts in conjunction with user authorization.
> **Note:** this is a "general" document, and not specific to this particular service client. In particular, you may find that the examples in this document are for a different client. All legacy REST clients follow the same usage patterns, and you should be able to adapt the provided examples to the client you are using.
> **Note:** this is a "general" document, and not specific to this particular service client. In particular, you may find that the examples in this document are for a different client. All simple REST clients follow the same usage patterns, and you should be able to adapt the provided examples to the client you are using.
## Prerequisites

10
docs/usage-guide.md
View File

@ -1,8 +1,8 @@
# Usage Guide for Legacy REST Clients
# Usage Guide for Simple REST Clients
This document provides all the basic information you need to start using the legacy REST clients for Google APIs. It covers important library concepts, shows examples for various use cases, and gives links to more information.
This document provides all the basic information you need to start using the simple REST clients for Google APIs. It covers important library concepts, shows examples for various use cases, and gives links to more information.
> **Note:** this is a "general" document, and not specific to this particular service client. In particular, you may find that the examples in this document are for a different client. All legacy REST clients follow the same usage patterns, and you should be able to adapt the provided examples to the client you are using.
> **Note:** this is a "general" document, and not specific to this particular service client. In particular, you may find that the examples in this document are for a different client. All simple REST clients follow the same usage patterns, and you should be able to adapt the provided examples to the client you are using.
## Before you begin
@ -58,11 +58,11 @@ drive.get_file(metadata.id, download_dest: '/tmp/myfile.txt')
## Authorization
All API calls need to be authenticated, to ensure authorized access to data, and for proper accounting for quota and billing. Google legacy REST clients support several different types of authentication, including OAuth 2.0, service accounts, API keys, and default credentials. Detailed documentation, including examples of several common authentication flows, is provided in the separate [Auth Guide](auth-guide.md). In the present document, we will discuss a few basic cases to get started.
All API calls need to be authenticated, to ensure authorized access to data, and for proper accounting for quota and billing. Google simple REST clients support several different types of authentication, including OAuth 2.0, service accounts, API keys, and default credentials. Detailed documentation, including examples of several common authentication flows, is provided in the separate [Auth Guide](auth-guide.md). In the present document, we will discuss a few basic cases to get started.
### Auth libraries
Most auth functionality is provided in two separate Ruby gems, which legacy REST clients bring in as dependencies.
Most auth functionality is provided in two separate Ruby gems, which simple REST clients bring in as dependencies.
* The [signet](https://github.com/google/signet) gem is a basic implementation of [OAuth 2](https://developers.google.com/accounts/docs/OAuth2). For calls that require per-user authorization, it can be used to direct the OAuth flow needed to obtain authorization.
* The [googleauth](https://github.com/google/google-auth-library-ruby) gem builds atop signet, and offers a simple way to get credentials for use in Google APIs when auth is independent of the user. In particular, this is the recommend approach for many Cloud APIs.

4
generated/google-apis-abusiveexperiencereport_v1/CHANGELOG.md
View File

@ -1,7 +1,7 @@
# Release history for google-apis-abusiveexperiencereport_v1
### v0.1.0 (2021-01-01)
### v0.1.0 (2021-01-07)
* Regenerated using generator version 0.1.1
* Regenerated from discovery document revision 20200803
* Regenerated using generator version 0.1.0

16
generated/google-apis-abusiveexperiencereport_v1/OVERVIEW.md
View File

@ -1,4 +1,4 @@
# Legacy REST client for version V1 of the Abusive Experience Report API
# Simple REST client for version V1 of the Abusive Experience Report API
This is a simple client library for version V1 of the Abusive Experience Report API. It provides:
@ -7,7 +7,7 @@ This is a simple client library for version V1 of the Abusive Experience Report
* Integration with the googleauth gem for authentication using OAuth, API keys, and service accounts.
* Control of retry, pagination, and timeouts.
Note that although this client library is supported and will continue to be updated to track changes to the service, it is considered legacy. A more modern client may be available for many Google services, especially Cloud Platform services. See the section below titled *Which client should I use?* for more information.
Note that although this client library is supported and will continue to be updated to track changes to the service, it is otherwise considered complete and not under active development. Many Google services, especially Google Cloud Platform services, may provide a more modern client that is under more active development and improvement. See the section below titled *Which client should I use?* for more information.
## Getting started
@ -58,26 +58,26 @@ See the class reference docs for information on the methods you can call from a
## Documentation
More detailed descriptions of the Google legacy REST clients are available in two documents.
More detailed descriptions of the Google simple REST clients are available in two documents.
* The [Usage Guide](https://github.com/googleapis/google-api-ruby-client/blob/master/docs/usage-guide.md) discusses how to make API calls, how to use the provided data structures, and how to work the various features of the client library, including media upload and download, error handling, retries, pagination, and logging.
* The [Auth Guide](https://github.com/googleapis/google-api-ruby-client/blob/master/docs/auth-guide.md) discusses authentication in the client libraries, including API keys, OAuth 2.0, service accounts, and environment variables.
(Note: the above documents are written for the legacy clients in general, and their examples may not reflect the Abusiveexperiencereport service in particular.)
(Note: the above documents are written for the simple REST clients in general, and their examples may not reflect the Abusiveexperiencereport service in particular.)
For reference information on specific calls in the Abusive Experience Report API, see the {Google::Apis::AbusiveexperiencereportV1::AbusiveExperienceReportService class reference docs}.
## Which client should I use?
Google provides two types of Ruby API client libraries: **legacy REST clients** and **modern clients**.
Google provides two types of Ruby API client libraries: **simple REST clients** and **modern clients**.
This library, `google-apis-abusiveexperiencereport_v1`, is a legacy REST client. You can identify legacy clients by their gem names, which are always in the form `google-apis-<servicename>_<serviceversion>`. The legacy REST clients connect to HTTP/JSON REST endpoints and are automatically generated from service discovery documents. They support most API functionality, but their class interfaces are sometimes awkward.
This library, `google-apis-abusiveexperiencereport_v1`, is a simple REST client. You can identify these clients by their gem names, which are always in the form `google-apis-<servicename>_<serviceversion>`. The simple REST clients connect to HTTP/JSON REST endpoints and are automatically generated from service discovery documents. They support most API functionality, but their class interfaces are sometimes awkward.
Modern clients are produced by a modern code generator, combined with hand-crafted functionality for some services. Most modern clients connect to high-performance gRPC endpoints, although a few are backed by REST services. Modern clients are available for many Google services, especially Cloud Platform services, but do not yet support all the services covered by the legacy clients.
Modern clients are produced by a modern code generator, sometimes combined with hand-crafted functionality. Most modern clients connect to high-performance gRPC endpoints, although a few are backed by REST services. Modern clients are available for many Google services, especially Google Cloud Platform services, but do not yet support all the services covered by the simple clients.
Gem names for modern clients are often of the form `google-cloud-<service_name>`. (For example, [google-cloud-pubsub](https://rubygems.org/gems/google-cloud-pubsub).) Note that most modern clients also have corresponding "versioned" gems with names like `google-cloud-<service_name>-<version>`. (For example, [google-cloud-pubsub-v1](https://rubygems.org/gems/google-cloud-pubsub-v1).) The "versioned" gems can be used directly, but often provide lower-level interfaces. In most cases, the main gem is recommended.
**For most users, we recommend the modern client, if one is available.** Compared with legacy clients, modern clients are generally much easier to use and more Ruby-like, support more advanced features such as streaming and long-running operations, and often provide much better performance. You may consider using a legacy client instead, if a modern client is not yet available for the service you want to use, or if you are not able to use gRPC on your infrastructure.
**For most users, we recommend the modern client, if one is available.** Compared with simple clients, modern clients are generally much easier to use and more Ruby-like, support more advanced features such as streaming and long-running operations, and often provide much better performance. You may consider using a simple client instead, if a modern client is not yet available for the service you want to use, or if you are not able to use gRPC on your infrastructure.
The [product documentation](https://developers.google.com/abusive-experience-report/) may provide guidance regarding the preferred client library to use.

6
generated/google-apis-abusiveexperiencereport_v1/google-apis-abusiveexperiencereport_v1.gemspec
View File

@ -5,10 +5,10 @@ Gem::Specification.new do |gem|
gem.version = Google::Apis::AbusiveexperiencereportV1::GEM_VERSION
gem.authors = ["Google LLC"]
gem.email = "googleapis-packages@google.com"
gem.summary = "Legacy REST client for Abusive Experience Report API V1"
gem.summary = "Simple REST client for Abusive Experience Report API V1"
gem.description =
"This is the legacy REST client for Abusive Experience Report API V1." \
" Legacy REST clients are simple Ruby libraries that provide access to" \
"This is the simple REST client for Abusive Experience Report API V1." \
" Simple REST clients are Ruby client libraries that provide access to" \
" Google services via their HTTP REST API endpoints. These libraries are" \
" generated and updated automatically based on the discovery documents" \
" published by the service, and they handle most concerns such as" \

2
generated/google-apis-abusiveexperiencereport_v1/lib/google/apis/abusiveexperiencereport_v1/gem_version.rb
View File

@ -19,7 +19,7 @@ module Google
GEM_VERSION = "0.1.0"
# Version of the code generator used to generate this client
GENERATOR_VERSION = "0.1.0"
GENERATOR_VERSION = "0.1.1"
# Revision of the discovery document this client was generated from
REVISION = "20200803"

4
generated/google-apis-acceleratedmobilepageurl_v1/CHANGELOG.md
View File

@ -1,7 +1,7 @@
# Release history for google-apis-acceleratedmobilepageurl_v1
### v0.1.0 (2021-01-01)
### v0.1.0 (2021-01-07)
* Regenerated using generator version 0.1.1
* Regenerated from discovery document revision 20200916
* Regenerated using generator version 0.1.0

16
generated/google-apis-acceleratedmobilepageurl_v1/OVERVIEW.md
View File

@ -1,4 +1,4 @@
# Legacy REST client for version V1 of the Accelerated Mobile Pages (AMP) URL API
# Simple REST client for version V1 of the Accelerated Mobile Pages (AMP) URL API
This is a simple client library for version V1 of the Accelerated Mobile Pages (AMP) URL API. It provides:
@ -7,7 +7,7 @@ This is a simple client library for version V1 of the Accelerated Mobile Pages (
* Integration with the googleauth gem for authentication using OAuth, API keys, and service accounts.
* Control of retry, pagination, and timeouts.
Note that although this client library is supported and will continue to be updated to track changes to the service, it is considered legacy. A more modern client may be available for many Google services, especially Cloud Platform services. See the section below titled *Which client should I use?* for more information.
Note that although this client library is supported and will continue to be updated to track changes to the service, it is otherwise considered complete and not under active development. Many Google services, especially Google Cloud Platform services, may provide a more modern client that is under more active development and improvement. See the section below titled *Which client should I use?* for more information.
## Getting started
@ -58,26 +58,26 @@ See the class reference docs for information on the methods you can call from a
## Documentation
More detailed descriptions of the Google legacy REST clients are available in two documents.
More detailed descriptions of the Google simple REST clients are available in two documents.
* The [Usage Guide](https://github.com/googleapis/google-api-ruby-client/blob/master/docs/usage-guide.md) discusses how to make API calls, how to use the provided data structures, and how to work the various features of the client library, including media upload and download, error handling, retries, pagination, and logging.
* The [Auth Guide](https://github.com/googleapis/google-api-ruby-client/blob/master/docs/auth-guide.md) discusses authentication in the client libraries, including API keys, OAuth 2.0, service accounts, and environment variables.
(Note: the above documents are written for the legacy clients in general, and their examples may not reflect the Acceleratedmobilepageurl service in particular.)
(Note: the above documents are written for the simple REST clients in general, and their examples may not reflect the Acceleratedmobilepageurl service in particular.)
For reference information on specific calls in the Accelerated Mobile Pages (AMP) URL API, see the {Google::Apis::AcceleratedmobilepageurlV1::AcceleratedmobilepageurlService class reference docs}.
## Which client should I use?
Google provides two types of Ruby API client libraries: **legacy REST clients** and **modern clients**.
Google provides two types of Ruby API client libraries: **simple REST clients** and **modern clients**.
This library, `google-apis-acceleratedmobilepageurl_v1`, is a legacy REST client. You can identify legacy clients by their gem names, which are always in the form `google-apis-<servicename>_<serviceversion>`. The legacy REST clients connect to HTTP/JSON REST endpoints and are automatically generated from service discovery documents. They support most API functionality, but their class interfaces are sometimes awkward.
This library, `google-apis-acceleratedmobilepageurl_v1`, is a simple REST client. You can identify these clients by their gem names, which are always in the form `google-apis-<servicename>_<serviceversion>`. The simple REST clients connect to HTTP/JSON REST endpoints and are automatically generated from service discovery documents. They support most API functionality, but their class interfaces are sometimes awkward.
Modern clients are produced by a modern code generator, combined with hand-crafted functionality for some services. Most modern clients connect to high-performance gRPC endpoints, although a few are backed by REST services. Modern clients are available for many Google services, especially Cloud Platform services, but do not yet support all the services covered by the legacy clients.
Modern clients are produced by a modern code generator, sometimes combined with hand-crafted functionality. Most modern clients connect to high-performance gRPC endpoints, although a few are backed by REST services. Modern clients are available for many Google services, especially Google Cloud Platform services, but do not yet support all the services covered by the simple clients.
Gem names for modern clients are often of the form `google-cloud-<service_name>`. (For example, [google-cloud-pubsub](https://rubygems.org/gems/google-cloud-pubsub).) Note that most modern clients also have corresponding "versioned" gems with names like `google-cloud-<service_name>-<version>`. (For example, [google-cloud-pubsub-v1](https://rubygems.org/gems/google-cloud-pubsub-v1).) The "versioned" gems can be used directly, but often provide lower-level interfaces. In most cases, the main gem is recommended.
**For most users, we recommend the modern client, if one is available.** Compared with legacy clients, modern clients are generally much easier to use and more Ruby-like, support more advanced features such as streaming and long-running operations, and often provide much better performance. You may consider using a legacy client instead, if a modern client is not yet available for the service you want to use, or if you are not able to use gRPC on your infrastructure.
**For most users, we recommend the modern client, if one is available.** Compared with simple clients, modern clients are generally much easier to use and more Ruby-like, support more advanced features such as streaming and long-running operations, and often provide much better performance. You may consider using a simple client instead, if a modern client is not yet available for the service you want to use, or if you are not able to use gRPC on your infrastructure.
The [product documentation](https://developers.google.com/amp/cache/) may provide guidance regarding the preferred client library to use.

6
generated/google-apis-acceleratedmobilepageurl_v1/google-apis-acceleratedmobilepageurl_v1.gemspec
View File

@ -5,10 +5,10 @@ Gem::Specification.new do |gem|
gem.version = Google::Apis::AcceleratedmobilepageurlV1::GEM_VERSION
gem.authors = ["Google LLC"]
gem.email = "googleapis-packages@google.com"
gem.summary = "Legacy REST client for Accelerated Mobile Pages (AMP) URL API V1"
gem.summary = "Simple REST client for Accelerated Mobile Pages (AMP) URL API V1"
gem.description =
"This is the legacy REST client for Accelerated Mobile Pages (AMP) URL API V1." \
" Legacy REST clients are simple Ruby libraries that provide access to" \
"This is the simple REST client for Accelerated Mobile Pages (AMP) URL API V1." \
" Simple REST clients are Ruby client libraries that provide access to" \
" Google services via their HTTP REST API endpoints. These libraries are" \
" generated and updated automatically based on the discovery documents" \
" published by the service, and they handle most concerns such as" \

2
generated/google-apis-acceleratedmobilepageurl_v1/lib/google/apis/acceleratedmobilepageurl_v1/gem_version.rb
View File

@ -19,7 +19,7 @@ module Google
GEM_VERSION = "0.1.0"
# Version of the code generator used to generate this client
GENERATOR_VERSION = "0.1.0"
GENERATOR_VERSION = "0.1.1"
# Revision of the discovery document this client was generated from
REVISION = "20200916"

4
generated/google-apis-accessapproval_v1/CHANGELOG.md
View File

@ -1,7 +1,7 @@
# Release history for google-apis-accessapproval_v1
### v0.1.0 (2021-01-01)
### v0.1.0 (2021-01-07)
* Regenerated using generator version 0.1.1
* Regenerated from discovery document revision 20201030
* Regenerated using generator version 0.1.0

16
generated/google-apis-accessapproval_v1/OVERVIEW.md
View File

@ -1,4 +1,4 @@
# Legacy REST client for version V1 of the Access Approval API
# Simple REST client for version V1 of the Access Approval API
This is a simple client library for version V1 of the Access Approval API. It provides:
@ -7,7 +7,7 @@ This is a simple client library for version V1 of the Access Approval API. It pr
* Integration with the googleauth gem for authentication using OAuth, API keys, and service accounts.
* Control of retry, pagination, and timeouts.
Note that although this client library is supported and will continue to be updated to track changes to the service, it is considered legacy. A more modern client may be available for many Google services, especially Cloud Platform services. See the section below titled *Which client should I use?* for more information.
Note that although this client library is supported and will continue to be updated to track changes to the service, it is otherwise considered complete and not under active development. Many Google services, especially Google Cloud Platform services, may provide a more modern client that is under more active development and improvement. See the section below titled *Which client should I use?* for more information.
## Getting started
@ -58,26 +58,26 @@ See the class reference docs for information on the methods you can call from a
## Documentation
More detailed descriptions of the Google legacy REST clients are available in two documents.
More detailed descriptions of the Google simple REST clients are available in two documents.
* The [Usage Guide](https://github.com/googleapis/google-api-ruby-client/blob/master/docs/usage-guide.md) discusses how to make API calls, how to use the provided data structures, and how to work the various features of the client library, including media upload and download, error handling, retries, pagination, and logging.
* The [Auth Guide](https://github.com/googleapis/google-api-ruby-client/blob/master/docs/auth-guide.md) discusses authentication in the client libraries, including API keys, OAuth 2.0, service accounts, and environment variables.
(Note: the above documents are written for the legacy clients in general, and their examples may not reflect the Accessapproval service in particular.)
(Note: the above documents are written for the simple REST clients in general, and their examples may not reflect the Accessapproval service in particular.)
For reference information on specific calls in the Access Approval API, see the {Google::Apis::AccessapprovalV1::AccessApprovalService class reference docs}.
## Which client should I use?
Google provides two types of Ruby API client libraries: **legacy REST clients** and **modern clients**.
Google provides two types of Ruby API client libraries: **simple REST clients** and **modern clients**.
This library, `google-apis-accessapproval_v1`, is a legacy REST client. You can identify legacy clients by their gem names, which are always in the form `google-apis-<servicename>_<serviceversion>`. The legacy REST clients connect to HTTP/JSON REST endpoints and are automatically generated from service discovery documents. They support most API functionality, but their class interfaces are sometimes awkward.
This library, `google-apis-accessapproval_v1`, is a simple REST client. You can identify these clients by their gem names, which are always in the form `google-apis-<servicename>_<serviceversion>`. The simple REST clients connect to HTTP/JSON REST endpoints and are automatically generated from service discovery documents. They support most API functionality, but their class interfaces are sometimes awkward.
Modern clients are produced by a modern code generator, combined with hand-crafted functionality for some services. Most modern clients connect to high-performance gRPC endpoints, although a few are backed by REST services. Modern clients are available for many Google services, especially Cloud Platform services, but do not yet support all the services covered by the legacy clients.
Modern clients are produced by a modern code generator, sometimes combined with hand-crafted functionality. Most modern clients connect to high-performance gRPC endpoints, although a few are backed by REST services. Modern clients are available for many Google services, especially Google Cloud Platform services, but do not yet support all the services covered by the simple clients.
Gem names for modern clients are often of the form `google-cloud-<service_name>`. (For example, [google-cloud-pubsub](https://rubygems.org/gems/google-cloud-pubsub).) Note that most modern clients also have corresponding "versioned" gems with names like `google-cloud-<service_name>-<version>`. (For example, [google-cloud-pubsub-v1](https://rubygems.org/gems/google-cloud-pubsub-v1).) The "versioned" gems can be used directly, but often provide lower-level interfaces. In most cases, the main gem is recommended.
**For most users, we recommend the modern client, if one is available.** Compared with legacy clients, modern clients are generally much easier to use and more Ruby-like, support more advanced features such as streaming and long-running operations, and often provide much better performance. You may consider using a legacy client instead, if a modern client is not yet available for the service you want to use, or if you are not able to use gRPC on your infrastructure.
**For most users, we recommend the modern client, if one is available.** Compared with simple clients, modern clients are generally much easier to use and more Ruby-like, support more advanced features such as streaming and long-running operations, and often provide much better performance. You may consider using a simple client instead, if a modern client is not yet available for the service you want to use, or if you are not able to use gRPC on your infrastructure.
The [product documentation](https://cloud.google.com/access-approval/docs) may provide guidance regarding the preferred client library to use.

6
generated/google-apis-accessapproval_v1/google-apis-accessapproval_v1.gemspec
View File

@ -5,10 +5,10 @@ Gem::Specification.new do |gem|
gem.version = Google::Apis::AccessapprovalV1::GEM_VERSION
gem.authors = ["Google LLC"]
gem.email = "googleapis-packages@google.com"
gem.summary = "Legacy REST client for Access Approval API V1"
gem.summary = "Simple REST client for Access Approval API V1"
gem.description =
"This is the legacy REST client for Access Approval API V1." \
" Legacy REST clients are simple Ruby libraries that provide access to" \
"This is the simple REST client for Access Approval API V1." \
" Simple REST clients are Ruby client libraries that provide access to" \
" Google services via their HTTP REST API endpoints. These libraries are" \
" generated and updated automatically based on the discovery documents" \
" published by the service, and they handle most concerns such as" \

2
generated/google-apis-accessapproval_v1/lib/google/apis/accessapproval_v1/gem_version.rb
View File

@ -19,7 +19,7 @@ module Google
GEM_VERSION = "0.1.0"
# Version of the code generator used to generate this client
GENERATOR_VERSION = "0.1.0"
GENERATOR_VERSION = "0.1.1"
# Revision of the discovery document this client was generated from
REVISION = "20201030"

4
generated/google-apis-accesscontextmanager_v1/CHANGELOG.md
View File

@ -1,7 +1,7 @@
# Release history for google-apis-accesscontextmanager_v1
### v0.1.0 (2021-01-01)
### v0.1.0 (2021-01-07)
* Regenerated using generator version 0.1.1
* Regenerated from discovery document revision 20201210
* Regenerated using generator version 0.1.0

16
generated/google-apis-accesscontextmanager_v1/OVERVIEW.md
View File

@ -1,4 +1,4 @@
# Legacy REST client for version V1 of the Access Context Manager API
# Simple REST client for version V1 of the Access Context Manager API
This is a simple client library for version V1 of the Access Context Manager API. It provides:
@ -7,7 +7,7 @@ This is a simple client library for version V1 of the Access Context Manager API
* Integration with the googleauth gem for authentication using OAuth, API keys, and service accounts.
* Control of retry, pagination, and timeouts.
Note that although this client library is supported and will continue to be updated to track changes to the service, it is considered legacy. A more modern client may be available for many Google services, especially Cloud Platform services. See the section below titled *Which client should I use?* for more information.
Note that although this client library is supported and will continue to be updated to track changes to the service, it is otherwise considered complete and not under active development. Many Google services, especially Google Cloud Platform services, may provide a more modern client that is under more active development and improvement. See the section below titled *Which client should I use?* for more information.
## Getting started
@ -58,26 +58,26 @@ See the class reference docs for information on the methods you can call from a
## Documentation
More detailed descriptions of the Google legacy REST clients are available in two documents.
More detailed descriptions of the Google simple REST clients are available in two documents.
* The [Usage Guide](https://github.com/googleapis/google-api-ruby-client/blob/master/docs/usage-guide.md) discusses how to make API calls, how to use the provided data structures, and how to work the various features of the client library, including media upload and download, error handling, retries, pagination, and logging.
* The [Auth Guide](https://github.com/googleapis/google-api-ruby-client/blob/master/docs/auth-guide.md) discusses authentication in the client libraries, including API keys, OAuth 2.0, service accounts, and environment variables.
(Note: the above documents are written for the legacy clients in general, and their examples may not reflect the Accesscontextmanager service in particular.)
(Note: the above documents are written for the simple REST clients in general, and their examples may not reflect the Accesscontextmanager service in particular.)
For reference information on specific calls in the Access Context Manager API, see the {Google::Apis::AccesscontextmanagerV1::AccessContextManagerService class reference docs}.
## Which client should I use?
Google provides two types of Ruby API client libraries: **legacy REST clients** and **modern clients**.
Google provides two types of Ruby API client libraries: **simple REST clients** and **modern clients**.
This library, `google-apis-accesscontextmanager_v1`, is a legacy REST client. You can identify legacy clients by their gem names, which are always in the form `google-apis-<servicename>_<serviceversion>`. The legacy REST clients connect to HTTP/JSON REST endpoints and are automatically generated from service discovery documents. They support most API functionality, but their class interfaces are sometimes awkward.
This library, `google-apis-accesscontextmanager_v1`, is a simple REST client. You can identify these clients by their gem names, which are always in the form `google-apis-<servicename>_<serviceversion>`. The simple REST clients connect to HTTP/JSON REST endpoints and are automatically generated from service discovery documents. They support most API functionality, but their class interfaces are sometimes awkward.
Modern clients are produced by a modern code generator, combined with hand-crafted functionality for some services. Most modern clients connect to high-performance gRPC endpoints, although a few are backed by REST services. Modern clients are available for many Google services, especially Cloud Platform services, but do not yet support all the services covered by the legacy clients.
Modern clients are produced by a modern code generator, sometimes combined with hand-crafted functionality. Most modern clients connect to high-performance gRPC endpoints, although a few are backed by REST services. Modern clients are available for many Google services, especially Google Cloud Platform services, but do not yet support all the services covered by the simple clients.
Gem names for modern clients are often of the form `google-cloud-<service_name>`. (For example, [google-cloud-pubsub](https://rubygems.org/gems/google-cloud-pubsub).) Note that most modern clients also have corresponding "versioned" gems with names like `google-cloud-<service_name>-<version>`. (For example, [google-cloud-pubsub-v1](https://rubygems.org/gems/google-cloud-pubsub-v1).) The "versioned" gems can be used directly, but often provide lower-level interfaces. In most cases, the main gem is recommended.
**For most users, we recommend the modern client, if one is available.** Compared with legacy clients, modern clients are generally much easier to use and more Ruby-like, support more advanced features such as streaming and long-running operations, and often provide much better performance. You may consider using a legacy client instead, if a modern client is not yet available for the service you want to use, or if you are not able to use gRPC on your infrastructure.
**For most users, we recommend the modern client, if one is available.** Compared with simple clients, modern clients are generally much easier to use and more Ruby-like, support more advanced features such as streaming and long-running operations, and often provide much better performance. You may consider using a simple client instead, if a modern client is not yet available for the service you want to use, or if you are not able to use gRPC on your infrastructure.
The [product documentation](https://cloud.google.com/access-context-manager/docs/reference/rest/) may provide guidance regarding the preferred client library to use.

6
generated/google-apis-accesscontextmanager_v1/google-apis-accesscontextmanager_v1.gemspec
View File

@ -5,10 +5,10 @@ Gem::Specification.new do |gem|
gem.version = Google::Apis::AccesscontextmanagerV1::GEM_VERSION
gem.authors = ["Google LLC"]
gem.email = "googleapis-packages@google.com"
gem.summary = "Legacy REST client for Access Context Manager API V1"
gem.summary = "Simple REST client for Access Context Manager API V1"
gem.description =
"This is the legacy REST client for Access Context Manager API V1." \
" Legacy REST clients are simple Ruby libraries that provide access to" \
"This is the simple REST client for Access Context Manager API V1." \
" Simple REST clients are Ruby client libraries that provide access to" \
" Google services via their HTTP REST API endpoints. These libraries are" \
" generated and updated automatically based on the discovery documents" \
" published by the service, and they handle most concerns such as" \

2
generated/google-apis-accesscontextmanager_v1/lib/google/apis/accesscontextmanager_v1/gem_version.rb
View File

@ -19,7 +19,7 @@ module Google
GEM_VERSION = "0.1.0"
# Version of the code generator used to generate this client
GENERATOR_VERSION = "0.1.0"
GENERATOR_VERSION = "0.1.1"
# Revision of the discovery document this client was generated from
REVISION = "20201210"

4
generated/google-apis-accesscontextmanager_v1beta/CHANGELOG.md
View File

@ -1,7 +1,7 @@
# Release history for google-apis-accesscontextmanager_v1beta
### v0.1.0 (2021-01-01)
### v0.1.0 (2021-01-07)
* Regenerated using generator version 0.1.1
* Regenerated from discovery document revision 20200825
* Regenerated using generator version 0.1.0

16
generated/google-apis-accesscontextmanager_v1beta/OVERVIEW.md
View File

@ -1,4 +1,4 @@
# Legacy REST client for version V1beta of the Access Context Manager API
# Simple REST client for version V1beta of the Access Context Manager API
This is a simple client library for version V1beta of the Access Context Manager API. It provides:
@ -7,7 +7,7 @@ This is a simple client library for version V1beta of the Access Context Manager
* Integration with the googleauth gem for authentication using OAuth, API keys, and service accounts.
* Control of retry, pagination, and timeouts.
Note that although this client library is supported and will continue to be updated to track changes to the service, it is considered legacy. A more modern client may be available for many Google services, especially Cloud Platform services. See the section below titled *Which client should I use?* for more information.
Note that although this client library is supported and will continue to be updated to track changes to the service, it is otherwise considered complete and not under active development. Many Google services, especially Google Cloud Platform services, may provide a more modern client that is under more active development and improvement. See the section below titled *Which client should I use?* for more information.
## Getting started
@ -58,26 +58,26 @@ See the class reference docs for information on the methods you can call from a
## Documentation
More detailed descriptions of the Google legacy REST clients are available in two documents.
More detailed descriptions of the Google simple REST clients are available in two documents.
* The [Usage Guide](https://github.com/googleapis/google-api-ruby-client/blob/master/docs/usage-guide.md) discusses how to make API calls, how to use the provided data structures, and how to work the various features of the client library, including media upload and download, error handling, retries, pagination, and logging.
* The [Auth Guide](https://github.com/googleapis/google-api-ruby-client/blob/master/docs/auth-guide.md) discusses authentication in the client libraries, including API keys, OAuth 2.0, service accounts, and environment variables.
(Note: the above documents are written for the legacy clients in general, and their examples may not reflect the Accesscontextmanager service in particular.)
(Note: the above documents are written for the simple REST clients in general, and their examples may not reflect the Accesscontextmanager service in particular.)
For reference information on specific calls in the Access Context Manager API, see the {Google::Apis::AccesscontextmanagerV1beta::AccessContextManagerService class reference docs}.
## Which client should I use?
Google provides two types of Ruby API client libraries: **legacy REST clients** and **modern clients**.
Google provides two types of Ruby API client libraries: **simple REST clients** and **modern clients**.
This library, `google-apis-accesscontextmanager_v1beta`, is a legacy REST client. You can identify legacy clients by their gem names, which are always in the form `google-apis-<servicename>_<serviceversion>`. The legacy REST clients connect to HTTP/JSON REST endpoints and are automatically generated from service discovery documents. They support most API functionality, but their class interfaces are sometimes awkward.
This library, `google-apis-accesscontextmanager_v1beta`, is a simple REST client. You can identify these clients by their gem names, which are always in the form `google-apis-<servicename>_<serviceversion>`. The simple REST clients connect to HTTP/JSON REST endpoints and are automatically generated from service discovery documents. They support most API functionality, but their class interfaces are sometimes awkward.
Modern clients are produced by a modern code generator, combined with hand-crafted functionality for some services. Most modern clients connect to high-performance gRPC endpoints, although a few are backed by REST services. Modern clients are available for many Google services, especially Cloud Platform services, but do not yet support all the services covered by the legacy clients.
Modern clients are produced by a modern code generator, sometimes combined with hand-crafted functionality. Most modern clients connect to high-performance gRPC endpoints, although a few are backed by REST services. Modern clients are available for many Google services, especially Google Cloud Platform services, but do not yet support all the services covered by the simple clients.
Gem names for modern clients are often of the form `google-cloud-<service_name>`. (For example, [google-cloud-pubsub](https://rubygems.org/gems/google-cloud-pubsub).) Note that most modern clients also have corresponding "versioned" gems with names like `google-cloud-<service_name>-<version>`. (For example, [google-cloud-pubsub-v1](https://rubygems.org/gems/google-cloud-pubsub-v1).) The "versioned" gems can be used directly, but often provide lower-level interfaces. In most cases, the main gem is recommended.
**For most users, we recommend the modern client, if one is available.** Compared with legacy clients, modern clients are generally much easier to use and more Ruby-like, support more advanced features such as streaming and long-running operations, and often provide much better performance. You may consider using a legacy client instead, if a modern client is not yet available for the service you want to use, or if you are not able to use gRPC on your infrastructure.
**For most users, we recommend the modern client, if one is available.** Compared with simple clients, modern clients are generally much easier to use and more Ruby-like, support more advanced features such as streaming and long-running operations, and often provide much better performance. You may consider using a simple client instead, if a modern client is not yet available for the service you want to use, or if you are not able to use gRPC on your infrastructure.
The [product documentation](https://cloud.google.com/access-context-manager/docs/reference/rest/) may provide guidance regarding the preferred client library to use.

6
generated/google-apis-accesscontextmanager_v1beta/google-apis-accesscontextmanager_v1beta.gemspec
View File

@ -5,10 +5,10 @@ Gem::Specification.new do |gem|
gem.version = Google::Apis::AccesscontextmanagerV1beta::GEM_VERSION
gem.authors = ["Google LLC"]
gem.email = "googleapis-packages@google.com"
gem.summary = "Legacy REST client for Access Context Manager API V1beta"
gem.summary = "Simple REST client for Access Context Manager API V1beta"
gem.description =
"This is the legacy REST client for Access Context Manager API V1beta." \
" Legacy REST clients are simple Ruby libraries that provide access to" \
"This is the simple REST client for Access Context Manager API V1beta." \
" Simple REST clients are Ruby client libraries that provide access to" \
" Google services via their HTTP REST API endpoints. These libraries are" \
" generated and updated automatically based on the discovery documents" \
" published by the service, and they handle most concerns such as" \

2
generated/google-apis-accesscontextmanager_v1beta/lib/google/apis/accesscontextmanager_v1beta/gem_version.rb
View File

@ -19,7 +19,7 @@ module Google
GEM_VERSION = "0.1.0"
# Version of the code generator used to generate this client
GENERATOR_VERSION = "0.1.0"
GENERATOR_VERSION = "0.1.1"
# Revision of the discovery document this client was generated from
REVISION = "20200825"

4
generated/google-apis-adexchangebuyer2_v2beta1/CHANGELOG.md
View File

@ -1,7 +1,7 @@
# Release history for google-apis-adexchangebuyer2_v2beta1
### v0.1.0 (2021-01-01)
### v0.1.0 (2021-01-07)
* Regenerated using generator version 0.1.1
* Regenerated from discovery document revision 20201202
* Regenerated using generator version 0.1.0

16
generated/google-apis-adexchangebuyer2_v2beta1/OVERVIEW.md
View File

@ -1,4 +1,4 @@
# Legacy REST client for version V2beta1 of the Ad Exchange Buyer API II
# Simple REST client for version V2beta1 of the Ad Exchange Buyer API II
This is a simple client library for version V2beta1 of the Ad Exchange Buyer API II. It provides:
@ -7,7 +7,7 @@ This is a simple client library for version V2beta1 of the Ad Exchange Buyer API
* Integration with the googleauth gem for authentication using OAuth, API keys, and service accounts.
* Control of retry, pagination, and timeouts.
Note that although this client library is supported and will continue to be updated to track changes to the service, it is considered legacy. A more modern client may be available for many Google services, especially Cloud Platform services. See the section below titled *Which client should I use?* for more information.
Note that although this client library is supported and will continue to be updated to track changes to the service, it is otherwise considered complete and not under active development. Many Google services, especially Google Cloud Platform services, may provide a more modern client that is under more active development and improvement. See the section below titled *Which client should I use?* for more information.
## Getting started
@ -58,26 +58,26 @@ See the class reference docs for information on the methods you can call from a
## Documentation
More detailed descriptions of the Google legacy REST clients are available in two documents.
More detailed descriptions of the Google simple REST clients are available in two documents.
* The [Usage Guide](https://github.com/googleapis/google-api-ruby-client/blob/master/docs/usage-guide.md) discusses how to make API calls, how to use the provided data structures, and how to work the various features of the client library, including media upload and download, error handling, retries, pagination, and logging.
* The [Auth Guide](https://github.com/googleapis/google-api-ruby-client/blob/master/docs/auth-guide.md) discusses authentication in the client libraries, including API keys, OAuth 2.0, service accounts, and environment variables.
(Note: the above documents are written for the legacy clients in general, and their examples may not reflect the Adexchangebuyer2 service in particular.)
(Note: the above documents are written for the simple REST clients in general, and their examples may not reflect the Adexchangebuyer2 service in particular.)
For reference information on specific calls in the Ad Exchange Buyer API II, see the {Google::Apis::Adexchangebuyer2V2beta1::AdExchangeBuyerIIService class reference docs}.
## Which client should I use?
Google provides two types of Ruby API client libraries: **legacy REST clients** and **modern clients**.
Google provides two types of Ruby API client libraries: **simple REST clients** and **modern clients**.
This library, `google-apis-adexchangebuyer2_v2beta1`, is a legacy REST client. You can identify legacy clients by their gem names, which are always in the form `google-apis-<servicename>_<serviceversion>`. The legacy REST clients connect to HTTP/JSON REST endpoints and are automatically generated from service discovery documents. They support most API functionality, but their class interfaces are sometimes awkward.
This library, `google-apis-adexchangebuyer2_v2beta1`, is a simple REST client. You can identify these clients by their gem names, which are always in the form `google-apis-<servicename>_<serviceversion>`. The simple REST clients connect to HTTP/JSON REST endpoints and are automatically generated from service discovery documents. They support most API functionality, but their class interfaces are sometimes awkward.
Modern clients are produced by a modern code generator, combined with hand-crafted functionality for some services. Most modern clients connect to high-performance gRPC endpoints, although a few are backed by REST services. Modern clients are available for many Google services, especially Cloud Platform services, but do not yet support all the services covered by the legacy clients.
Modern clients are produced by a modern code generator, sometimes combined with hand-crafted functionality. Most modern clients connect to high-performance gRPC endpoints, although a few are backed by REST services. Modern clients are available for many Google services, especially Google Cloud Platform services, but do not yet support all the services covered by the simple clients.
Gem names for modern clients are often of the form `google-cloud-<service_name>`. (For example, [google-cloud-pubsub](https://rubygems.org/gems/google-cloud-pubsub).) Note that most modern clients also have corresponding "versioned" gems with names like `google-cloud-<service_name>-<version>`. (For example, [google-cloud-pubsub-v1](https://rubygems.org/gems/google-cloud-pubsub-v1).) The "versioned" gems can be used directly, but often provide lower-level interfaces. In most cases, the main gem is recommended.
**For most users, we recommend the modern client, if one is available.** Compared with legacy clients, modern clients are generally much easier to use and more Ruby-like, support more advanced features such as streaming and long-running operations, and often provide much better performance. You may consider using a legacy client instead, if a modern client is not yet available for the service you want to use, or if you are not able to use gRPC on your infrastructure.
**For most users, we recommend the modern client, if one is available.** Compared with simple clients, modern clients are generally much easier to use and more Ruby-like, support more advanced features such as streaming and long-running operations, and often provide much better performance. You may consider using a simple client instead, if a modern client is not yet available for the service you want to use, or if you are not able to use gRPC on your infrastructure.
The [product documentation](https://developers.google.com/authorized-buyers/apis/reference/rest/) may provide guidance regarding the preferred client library to use.

6
generated/google-apis-adexchangebuyer2_v2beta1/google-apis-adexchangebuyer2_v2beta1.gemspec
View File

@ -5,10 +5,10 @@ Gem::Specification.new do |gem|
gem.version = Google::Apis::Adexchangebuyer2V2beta1::GEM_VERSION
gem.authors = ["Google LLC"]
gem.email = "googleapis-packages@google.com"
gem.summary = "Legacy REST client for Ad Exchange Buyer API II V2beta1"
gem.summary = "Simple REST client for Ad Exchange Buyer API II V2beta1"
gem.description =
"This is the legacy REST client for Ad Exchange Buyer API II V2beta1." \
" Legacy REST clients are simple Ruby libraries that provide access to" \
"This is the simple REST client for Ad Exchange Buyer API II V2beta1." \
" Simple REST clients are Ruby client libraries that provide access to" \
" Google services via their HTTP REST API endpoints. These libraries are" \
" generated and updated automatically based on the discovery documents" \
" published by the service, and they handle most concerns such as" \

2
generated/google-apis-adexchangebuyer2_v2beta1/lib/google/apis/adexchangebuyer2_v2beta1/gem_version.rb
View File

@ -19,7 +19,7 @@ module Google
GEM_VERSION = "0.1.0"
# Version of the code generator used to generate this client
GENERATOR_VERSION = "0.1.0"
GENERATOR_VERSION = "0.1.1"
# Revision of the discovery document this client was generated from
REVISION = "20201202"

4
generated/google-apis-adexchangebuyer_v1_2/CHANGELOG.md
View File

@ -1,7 +1,7 @@
# Release history for google-apis-adexchangebuyer_v1_2
### v0.1.0 (2021-01-01)
### v0.1.0 (2021-01-07)
* Regenerated using generator version 0.1.1
* Regenerated from discovery document revision 20180222
* Regenerated using generator version 0.1.0

16
generated/google-apis-adexchangebuyer_v1_2/OVERVIEW.md
View File

@ -1,4 +1,4 @@
# Legacy REST client for version V1_2 of the Ad Exchange Buyer API
# Simple REST client for version V1_2 of the Ad Exchange Buyer API
This is a simple client library for version V1_2 of the Ad Exchange Buyer API. It provides:
@ -7,7 +7,7 @@ This is a simple client library for version V1_2 of the Ad Exchange Buyer API. I
* Integration with the googleauth gem for authentication using OAuth, API keys, and service accounts.
* Control of retry, pagination, and timeouts.
Note that although this client library is supported and will continue to be updated to track changes to the service, it is considered legacy. A more modern client may be available for many Google services, especially Cloud Platform services. See the section below titled *Which client should I use?* for more information.
Note that although this client library is supported and will continue to be updated to track changes to the service, it is otherwise considered complete and not under active development. Many Google services, especially Google Cloud Platform services, may provide a more modern client that is under more active development and improvement. See the section below titled *Which client should I use?* for more information.
## Getting started
@ -58,26 +58,26 @@ See the class reference docs for information on the methods you can call from a
## Documentation
More detailed descriptions of the Google legacy REST clients are available in two documents.
More detailed descriptions of the Google simple REST clients are available in two documents.
* The [Usage Guide](https://github.com/googleapis/google-api-ruby-client/blob/master/docs/usage-guide.md) discusses how to make API calls, how to use the provided data structures, and how to work the various features of the client library, including media upload and download, error handling, retries, pagination, and logging.
* The [Auth Guide](https://github.com/googleapis/google-api-ruby-client/blob/master/docs/auth-guide.md) discusses authentication in the client libraries, including API keys, OAuth 2.0, service accounts, and environment variables.
(Note: the above documents are written for the legacy clients in general, and their examples may not reflect the Adexchangebuyer service in particular.)
(Note: the above documents are written for the simple REST clients in general, and their examples may not reflect the Adexchangebuyer service in particular.)
For reference information on specific calls in the Ad Exchange Buyer API, see the {Google::Apis::AdexchangebuyerV1_2::AdExchangeBuyerService class reference docs}.
## Which client should I use?
Google provides two types of Ruby API client libraries: **legacy REST clients** and **modern clients**.
Google provides two types of Ruby API client libraries: **simple REST clients** and **modern clients**.
This library, `google-apis-adexchangebuyer_v1_2`, is a legacy REST client. You can identify legacy clients by their gem names, which are always in the form `google-apis-<servicename>_<serviceversion>`. The legacy REST clients connect to HTTP/JSON REST endpoints and are automatically generated from service discovery documents. They support most API functionality, but their class interfaces are sometimes awkward.
This library, `google-apis-adexchangebuyer_v1_2`, is a simple REST client. You can identify these clients by their gem names, which are always in the form `google-apis-<servicename>_<serviceversion>`. The simple REST clients connect to HTTP/JSON REST endpoints and are automatically generated from service discovery documents. They support most API functionality, but their class interfaces are sometimes awkward.
Modern clients are produced by a modern code generator, combined with hand-crafted functionality for some services. Most modern clients connect to high-performance gRPC endpoints, although a few are backed by REST services. Modern clients are available for many Google services, especially Cloud Platform services, but do not yet support all the services covered by the legacy clients.
Modern clients are produced by a modern code generator, sometimes combined with hand-crafted functionality. Most modern clients connect to high-performance gRPC endpoints, although a few are backed by REST services. Modern clients are available for many Google services, especially Google Cloud Platform services, but do not yet support all the services covered by the simple clients.
Gem names for modern clients are often of the form `google-cloud-<service_name>`. (For example, [google-cloud-pubsub](https://rubygems.org/gems/google-cloud-pubsub).) Note that most modern clients also have corresponding "versioned" gems with names like `google-cloud-<service_name>-<version>`. (For example, [google-cloud-pubsub-v1](https://rubygems.org/gems/google-cloud-pubsub-v1).) The "versioned" gems can be used directly, but often provide lower-level interfaces. In most cases, the main gem is recommended.
**For most users, we recommend the modern client, if one is available.** Compared with legacy clients, modern clients are generally much easier to use and more Ruby-like, support more advanced features such as streaming and long-running operations, and often provide much better performance. You may consider using a legacy client instead, if a modern client is not yet available for the service you want to use, or if you are not able to use gRPC on your infrastructure.
**For most users, we recommend the modern client, if one is available.** Compared with simple clients, modern clients are generally much easier to use and more Ruby-like, support more advanced features such as streaming and long-running operations, and often provide much better performance. You may consider using a simple client instead, if a modern client is not yet available for the service you want to use, or if you are not able to use gRPC on your infrastructure.
The [product documentation](https://developers.google.com/ad-exchange/buyer-rest) may provide guidance regarding the preferred client library to use.

6
generated/google-apis-adexchangebuyer_v1_2/google-apis-adexchangebuyer_v1_2.gemspec
View File

@ -5,10 +5,10 @@ Gem::Specification.new do |gem|
gem.version = Google::Apis::AdexchangebuyerV1_2::GEM_VERSION
gem.authors = ["Google LLC"]
gem.email = "googleapis-packages@google.com"
gem.summary = "Legacy REST client for Ad Exchange Buyer API V1_2"
gem.summary = "Simple REST client for Ad Exchange Buyer API V1_2"
gem.description =
"This is the legacy REST client for Ad Exchange Buyer API V1_2." \
" Legacy REST clients are simple Ruby libraries that provide access to" \
"This is the simple REST client for Ad Exchange Buyer API V1_2." \
" Simple REST clients are Ruby client libraries that provide access to" \
" Google services via their HTTP REST API endpoints. These libraries are" \
" generated and updated automatically based on the discovery documents" \
" published by the service, and they handle most concerns such as" \

2
generated/google-apis-adexchangebuyer_v1_2/lib/google/apis/adexchangebuyer_v1_2/gem_version.rb
View File

@ -19,7 +19,7 @@ module Google
GEM_VERSION = "0.1.0"
# Version of the code generator used to generate this client
GENERATOR_VERSION = "0.1.0"
GENERATOR_VERSION = "0.1.1"
# Revision of the discovery document this client was generated from
REVISION = "20180222"

4
generated/google-apis-adexchangebuyer_v1_3/CHANGELOG.md
View File

@ -1,7 +1,7 @@
# Release history for google-apis-adexchangebuyer_v1_3
### v0.1.0 (2021-01-01)
### v0.1.0 (2021-01-07)
* Regenerated using generator version 0.1.1
* Regenerated from discovery document revision 20191108
* Regenerated using generator version 0.1.0

16
generated/google-apis-adexchangebuyer_v1_3/OVERVIEW.md
View File

@ -1,4 +1,4 @@
# Legacy REST client for version V1_3 of the Ad Exchange Buyer API
# Simple REST client for version V1_3 of the Ad Exchange Buyer API
This is a simple client library for version V1_3 of the Ad Exchange Buyer API. It provides:
@ -7,7 +7,7 @@ This is a simple client library for version V1_3 of the Ad Exchange Buyer API. I
* Integration with the googleauth gem for authentication using OAuth, API keys, and service accounts.
* Control of retry, pagination, and timeouts.
Note that although this client library is supported and will continue to be updated to track changes to the service, it is considered legacy. A more modern client may be available for many Google services, especially Cloud Platform services. See the section below titled *Which client should I use?* for more information.
Note that although this client library is supported and will continue to be updated to track changes to the service, it is otherwise considered complete and not under active development. Many Google services, especially Google Cloud Platform services, may provide a more modern client that is under more active development and improvement. See the section below titled *Which client should I use?* for more information.
## Getting started
@ -58,26 +58,26 @@ See the class reference docs for information on the methods you can call from a
## Documentation
More detailed descriptions of the Google legacy REST clients are available in two documents.
More detailed descriptions of the Google simple REST clients are available in two documents.
* The [Usage Guide](https://github.com/googleapis/google-api-ruby-client/blob/master/docs/usage-guide.md) discusses how to make API calls, how to use the provided data structures, and how to work the various features of the client library, including media upload and download, error handling, retries, pagination, and logging.
* The [Auth Guide](https://github.com/googleapis/google-api-ruby-client/blob/master/docs/auth-guide.md) discusses authentication in the client libraries, including API keys, OAuth 2.0, service accounts, and environment variables.
(Note: the above documents are written for the legacy clients in general, and their examples may not reflect the Adexchangebuyer service in particular.)
(Note: the above documents are written for the simple REST clients in general, and their examples may not reflect the Adexchangebuyer service in particular.)
For reference information on specific calls in the Ad Exchange Buyer API, see the {Google::Apis::AdexchangebuyerV1_3::AdExchangeBuyerService class reference docs}.
## Which client should I use?
Google provides two types of Ruby API client libraries: **legacy REST clients** and **modern clients**.
Google provides two types of Ruby API client libraries: **simple REST clients** and **modern clients**.
This library, `google-apis-adexchangebuyer_v1_3`, is a legacy REST client. You can identify legacy clients by their gem names, which are always in the form `google-apis-<servicename>_<serviceversion>`. The legacy REST clients connect to HTTP/JSON REST endpoints and are automatically generated from service discovery documents. They support most API functionality, but their class interfaces are sometimes awkward.
This library, `google-apis-adexchangebuyer_v1_3`, is a simple REST client. You can identify these clients by their gem names, which are always in the form `google-apis-<servicename>_<serviceversion>`. The simple REST clients connect to HTTP/JSON REST endpoints and are automatically generated from service discovery documents. They support most API functionality, but their class interfaces are sometimes awkward.
Modern clients are produced by a modern code generator, combined with hand-crafted functionality for some services. Most modern clients connect to high-performance gRPC endpoints, although a few are backed by REST services. Modern clients are available for many Google services, especially Cloud Platform services, but do not yet support all the services covered by the legacy clients.
Modern clients are produced by a modern code generator, sometimes combined with hand-crafted functionality. Most modern clients connect to high-performance gRPC endpoints, although a few are backed by REST services. Modern clients are available for many Google services, especially Google Cloud Platform services, but do not yet support all the services covered by the simple clients.
Gem names for modern clients are often of the form `google-cloud-<service_name>`. (For example, [google-cloud-pubsub](https://rubygems.org/gems/google-cloud-pubsub).) Note that most modern clients also have corresponding "versioned" gems with names like `google-cloud-<service_name>-<version>`. (For example, [google-cloud-pubsub-v1](https://rubygems.org/gems/google-cloud-pubsub-v1).) The "versioned" gems can be used directly, but often provide lower-level interfaces. In most cases, the main gem is recommended.
**For most users, we recommend the modern client, if one is available.** Compared with legacy clients, modern clients are generally much easier to use and more Ruby-like, support more advanced features such as streaming and long-running operations, and often provide much better performance. You may consider using a legacy client instead, if a modern client is not yet available for the service you want to use, or if you are not able to use gRPC on your infrastructure.
**For most users, we recommend the modern client, if one is available.** Compared with simple clients, modern clients are generally much easier to use and more Ruby-like, support more advanced features such as streaming and long-running operations, and often provide much better performance. You may consider using a simple client instead, if a modern client is not yet available for the service you want to use, or if you are not able to use gRPC on your infrastructure.
The [product documentation](https://developers.google.com/ad-exchange/buyer-rest) may provide guidance regarding the preferred client library to use.

6
generated/google-apis-adexchangebuyer_v1_3/google-apis-adexchangebuyer_v1_3.gemspec
View File

@ -5,10 +5,10 @@ Gem::Specification.new do |gem|
gem.version = Google::Apis::AdexchangebuyerV1_3::GEM_VERSION
gem.authors = ["Google LLC"]
gem.email = "googleapis-packages@google.com"
gem.summary = "Legacy REST client for Ad Exchange Buyer API V1_3"
gem.summary = "Simple REST client for Ad Exchange Buyer API V1_3"
gem.description =
"This is the legacy REST client for Ad Exchange Buyer API V1_3." \
" Legacy REST clients are simple Ruby libraries that provide access to" \
"This is the simple REST client for Ad Exchange Buyer API V1_3." \
" Simple REST clients are Ruby client libraries that provide access to" \
" Google services via their HTTP REST API endpoints. These libraries are" \
" generated and updated automatically based on the discovery documents" \
" published by the service, and they handle most concerns such as" \

2
generated/google-apis-adexchangebuyer_v1_3/lib/google/apis/adexchangebuyer_v1_3/gem_version.rb
View File

@ -19,7 +19,7 @@ module Google
GEM_VERSION = "0.1.0"
# Version of the code generator used to generate this client
GENERATOR_VERSION = "0.1.0"
GENERATOR_VERSION = "0.1.1"
# Revision of the discovery document this client was generated from
REVISION = "20191108"

4
generated/google-apis-adexchangebuyer_v1_4/CHANGELOG.md
View File

@ -1,7 +1,7 @@
# Release history for google-apis-adexchangebuyer_v1_4
### v0.1.0 (2021-01-01)
### v0.1.0 (2021-01-07)
* Regenerated using generator version 0.1.1
* Regenerated from discovery document revision 20201004
* Regenerated using generator version 0.1.0

16
generated/google-apis-adexchangebuyer_v1_4/OVERVIEW.md
View File

@ -1,4 +1,4 @@
# Legacy REST client for version V1_4 of the Ad Exchange Buyer API
# Simple REST client for version V1_4 of the Ad Exchange Buyer API
This is a simple client library for version V1_4 of the Ad Exchange Buyer API. It provides:
@ -7,7 +7,7 @@ This is a simple client library for version V1_4 of the Ad Exchange Buyer API. I
* Integration with the googleauth gem for authentication using OAuth, API keys, and service accounts.
* Control of retry, pagination, and timeouts.
Note that although this client library is supported and will continue to be updated to track changes to the service, it is considered legacy. A more modern client may be available for many Google services, especially Cloud Platform services. See the section below titled *Which client should I use?* for more information.
Note that although this client library is supported and will continue to be updated to track changes to the service, it is otherwise considered complete and not under active development. Many Google services, especially Google Cloud Platform services, may provide a more modern client that is under more active development and improvement. See the section below titled *Which client should I use?* for more information.
## Getting started
@ -58,26 +58,26 @@ See the class reference docs for information on the methods you can call from a
## Documentation
More detailed descriptions of the Google legacy REST clients are available in two documents.
More detailed descriptions of the Google simple REST clients are available in two documents.
* The [Usage Guide](https://github.com/googleapis/google-api-ruby-client/blob/master/docs/usage-guide.md) discusses how to make API calls, how to use the provided data structures, and how to work the various features of the client library, including media upload and download, error handling, retries, pagination, and logging.
* The [Auth Guide](https://github.com/googleapis/google-api-ruby-client/blob/master/docs/auth-guide.md) discusses authentication in the client libraries, including API keys, OAuth 2.0, service accounts, and environment variables.
(Note: the above documents are written for the legacy clients in general, and their examples may not reflect the Adexchangebuyer service in particular.)
(Note: the above documents are written for the simple REST clients in general, and their examples may not reflect the Adexchangebuyer service in particular.)
For reference information on specific calls in the Ad Exchange Buyer API, see the {Google::Apis::AdexchangebuyerV1_4::AdExchangeBuyerService class reference docs}.
## Which client should I use?
Google provides two types of Ruby API client libraries: **legacy REST clients** and **modern clients**.
Google provides two types of Ruby API client libraries: **simple REST clients** and **modern clients**.
This library, `google-apis-adexchangebuyer_v1_4`, is a legacy REST client. You can identify legacy clients by their gem names, which are always in the form `google-apis-<servicename>_<serviceversion>`. The legacy REST clients connect to HTTP/JSON REST endpoints and are automatically generated from service discovery documents. They support most API functionality, but their class interfaces are sometimes awkward.
This library, `google-apis-adexchangebuyer_v1_4`, is a simple REST client. You can identify these clients by their gem names, which are always in the form `google-apis-<servicename>_<serviceversion>`. The simple REST clients connect to HTTP/JSON REST endpoints and are automatically generated from service discovery documents. They support most API functionality, but their class interfaces are sometimes awkward.
Modern clients are produced by a modern code generator, combined with hand-crafted functionality for some services. Most modern clients connect to high-performance gRPC endpoints, although a few are backed by REST services. Modern clients are available for many Google services, especially Cloud Platform services, but do not yet support all the services covered by the legacy clients.
Modern clients are produced by a modern code generator, sometimes combined with hand-crafted functionality. Most modern clients connect to high-performance gRPC endpoints, although a few are backed by REST services. Modern clients are available for many Google services, especially Google Cloud Platform services, but do not yet support all the services covered by the simple clients.
Gem names for modern clients are often of the form `google-cloud-<service_name>`. (For example, [google-cloud-pubsub](https://rubygems.org/gems/google-cloud-pubsub).) Note that most modern clients also have corresponding "versioned" gems with names like `google-cloud-<service_name>-<version>`. (For example, [google-cloud-pubsub-v1](https://rubygems.org/gems/google-cloud-pubsub-v1).) The "versioned" gems can be used directly, but often provide lower-level interfaces. In most cases, the main gem is recommended.
**For most users, we recommend the modern client, if one is available.** Compared with legacy clients, modern clients are generally much easier to use and more Ruby-like, support more advanced features such as streaming and long-running operations, and often provide much better performance. You may consider using a legacy client instead, if a modern client is not yet available for the service you want to use, or if you are not able to use gRPC on your infrastructure.
**For most users, we recommend the modern client, if one is available.** Compared with simple clients, modern clients are generally much easier to use and more Ruby-like, support more advanced features such as streaming and long-running operations, and often provide much better performance. You may consider using a simple client instead, if a modern client is not yet available for the service you want to use, or if you are not able to use gRPC on your infrastructure.
The [product documentation](https://developers.google.com/ad-exchange/buyer-rest) may provide guidance regarding the preferred client library to use.

6
generated/google-apis-adexchangebuyer_v1_4/google-apis-adexchangebuyer_v1_4.gemspec
View File

@ -5,10 +5,10 @@ Gem::Specification.new do |gem|
gem.version = Google::Apis::AdexchangebuyerV1_4::GEM_VERSION
gem.authors = ["Google LLC"]
gem.email = "googleapis-packages@google.com"
gem.summary = "Legacy REST client for Ad Exchange Buyer API V1_4"
gem.summary = "Simple REST client for Ad Exchange Buyer API V1_4"
gem.description =
"This is the legacy REST client for Ad Exchange Buyer API V1_4." \
" Legacy REST clients are simple Ruby libraries that provide access to" \
"This is the simple REST client for Ad Exchange Buyer API V1_4." \
" Simple REST clients are Ruby client libraries that provide access to" \
" Google services via their HTTP REST API endpoints. These libraries are" \
" generated and updated automatically based on the discovery documents" \
" published by the service, and they handle most concerns such as" \

2
generated/google-apis-adexchangebuyer_v1_4/lib/google/apis/adexchangebuyer_v1_4/gem_version.rb
View File

@ -19,7 +19,7 @@ module Google
GEM_VERSION = "0.1.0"
# Version of the code generator used to generate this client
GENERATOR_VERSION = "0.1.0"
GENERATOR_VERSION = "0.1.1"
# Revision of the discovery document this client was generated from
REVISION = "20201004"

4
generated/google-apis-adexperiencereport_v1/CHANGELOG.md
View File

@ -1,7 +1,7 @@
# Release history for google-apis-adexperiencereport_v1
### v0.1.0 (2021-01-01)
### v0.1.0 (2021-01-07)
* Regenerated using generator version 0.1.1
* Regenerated from discovery document revision 20200823
* Regenerated using generator version 0.1.0

16
generated/google-apis-adexperiencereport_v1/OVERVIEW.md
View File

@ -1,4 +1,4 @@
# Legacy REST client for version V1 of the Ad Experience Report API
# Simple REST client for version V1 of the Ad Experience Report API
This is a simple client library for version V1 of the Ad Experience Report API. It provides:
@ -7,7 +7,7 @@ This is a simple client library for version V1 of the Ad Experience Report API.
* Integration with the googleauth gem for authentication using OAuth, API keys, and service accounts.
* Control of retry, pagination, and timeouts.
Note that although this client library is supported and will continue to be updated to track changes to the service, it is considered legacy. A more modern client may be available for many Google services, especially Cloud Platform services. See the section below titled *Which client should I use?* for more information.
Note that although this client library is supported and will continue to be updated to track changes to the service, it is otherwise considered complete and not under active development. Many Google services, especially Google Cloud Platform services, may provide a more modern client that is under more active development and improvement. See the section below titled *Which client should I use?* for more information.
## Getting started
@ -58,26 +58,26 @@ See the class reference docs for information on the methods you can call from a
## Documentation
More detailed descriptions of the Google legacy REST clients are available in two documents.
More detailed descriptions of the Google simple REST clients are available in two documents.
* The [Usage Guide](https://github.com/googleapis/google-api-ruby-client/blob/master/docs/usage-guide.md) discusses how to make API calls, how to use the provided data structures, and how to work the various features of the client library, including media upload and download, error handling, retries, pagination, and logging.
* The [Auth Guide](https://github.com/googleapis/google-api-ruby-client/blob/master/docs/auth-guide.md) discusses authentication in the client libraries, including API keys, OAuth 2.0, service accounts, and environment variables.
(Note: the above documents are written for the legacy clients in general, and their examples may not reflect the Adexperiencereport service in particular.)
(Note: the above documents are written for the simple REST clients in general, and their examples may not reflect the Adexperiencereport service in particular.)
For reference information on specific calls in the Ad Experience Report API, see the {Google::Apis::AdexperiencereportV1::AdExperienceReportService class reference docs}.
## Which client should I use?
Google provides two types of Ruby API client libraries: **legacy REST clients** and **modern clients**.
Google provides two types of Ruby API client libraries: **simple REST clients** and **modern clients**.
This library, `google-apis-adexperiencereport_v1`, is a legacy REST client. You can identify legacy clients by their gem names, which are always in the form `google-apis-<servicename>_<serviceversion>`. The legacy REST clients connect to HTTP/JSON REST endpoints and are automatically generated from service discovery documents. They support most API functionality, but their class interfaces are sometimes awkward.
This library, `google-apis-adexperiencereport_v1`, is a simple REST client. You can identify these clients by their gem names, which are always in the form `google-apis-<servicename>_<serviceversion>`. The simple REST clients connect to HTTP/JSON REST endpoints and are automatically generated from service discovery documents. They support most API functionality, but their class interfaces are sometimes awkward.
Modern clients are produced by a modern code generator, combined with hand-crafted functionality for some services. Most modern clients connect to high-performance gRPC endpoints, although a few are backed by REST services. Modern clients are available for many Google services, especially Cloud Platform services, but do not yet support all the services covered by the legacy clients.
Modern clients are produced by a modern code generator, sometimes combined with hand-crafted functionality. Most modern clients connect to high-performance gRPC endpoints, although a few are backed by REST services. Modern clients are available for many Google services, especially Google Cloud Platform services, but do not yet support all the services covered by the simple clients.
Gem names for modern clients are often of the form `google-cloud-<service_name>`. (For example, [google-cloud-pubsub](https://rubygems.org/gems/google-cloud-pubsub).) Note that most modern clients also have corresponding "versioned" gems with names like `google-cloud-<service_name>-<version>`. (For example, [google-cloud-pubsub-v1](https://rubygems.org/gems/google-cloud-pubsub-v1).) The "versioned" gems can be used directly, but often provide lower-level interfaces. In most cases, the main gem is recommended.
**For most users, we recommend the modern client, if one is available.** Compared with legacy clients, modern clients are generally much easier to use and more Ruby-like, support more advanced features such as streaming and long-running operations, and often provide much better performance. You may consider using a legacy client instead, if a modern client is not yet available for the service you want to use, or if you are not able to use gRPC on your infrastructure.
**For most users, we recommend the modern client, if one is available.** Compared with simple clients, modern clients are generally much easier to use and more Ruby-like, support more advanced features such as streaming and long-running operations, and often provide much better performance. You may consider using a simple client instead, if a modern client is not yet available for the service you want to use, or if you are not able to use gRPC on your infrastructure.
The [product documentation](https://developers.google.com/ad-experience-report/) may provide guidance regarding the preferred client library to use.

6
generated/google-apis-adexperiencereport_v1/google-apis-adexperiencereport_v1.gemspec
View File

@ -5,10 +5,10 @@ Gem::Specification.new do |gem|
gem.version = Google::Apis::AdexperiencereportV1::GEM_VERSION
gem.authors = ["Google LLC"]
gem.email = "googleapis-packages@google.com"
gem.summary = "Legacy REST client for Ad Experience Report API V1"
gem.summary = "Simple REST client for Ad Experience Report API V1"
gem.description =
"This is the legacy REST client for Ad Experience Report API V1." \
" Legacy REST clients are simple Ruby libraries that provide access to" \
"This is the simple REST client for Ad Experience Report API V1." \
" Simple REST clients are Ruby client libraries that provide access to" \
" Google services via their HTTP REST API endpoints. These libraries are" \
" generated and updated automatically based on the discovery documents" \
" published by the service, and they handle most concerns such as" \

2
generated/google-apis-adexperiencereport_v1/lib/google/apis/adexperiencereport_v1/gem_version.rb
View File

@ -19,7 +19,7 @@ module Google
GEM_VERSION = "0.1.0"
# Version of the code generator used to generate this client
GENERATOR_VERSION = "0.1.0"
GENERATOR_VERSION = "0.1.1"
# Revision of the discovery document this client was generated from
REVISION = "20200823"

16
generated/google-apis-admin_datatransfer_v1/OVERVIEW.md
View File

@ -1,4 +1,4 @@
# Legacy REST client for version DatatransferV1 of the Admin SDK API
# Simple REST client for version DatatransferV1 of the Admin SDK API
This is a simple client library for version DatatransferV1 of the Admin SDK API. It provides:
@ -7,7 +7,7 @@ This is a simple client library for version DatatransferV1 of the Admin SDK API.
* Integration with the googleauth gem for authentication using OAuth, API keys, and service accounts.
* Control of retry, pagination, and timeouts.
Note that although this client library is supported and will continue to be updated to track changes to the service, it is considered legacy. A more modern client may be available for many Google services, especially Cloud Platform services. See the section below titled *Which client should I use?* for more information.
Note that although this client library is supported and will continue to be updated to track changes to the service, it is otherwise considered complete and not under active development. Many Google services, especially Google Cloud Platform services, may provide a more modern client that is under more active development and improvement. See the section below titled *Which client should I use?* for more information.
## Getting started
@ -58,26 +58,26 @@ See the class reference docs for information on the methods you can call from a
## Documentation
More detailed descriptions of the Google legacy REST clients are available in two documents.
More detailed descriptions of the Google simple REST clients are available in two documents.
* The [Usage Guide](https://github.com/googleapis/google-api-ruby-client/blob/master/docs/usage-guide.md) discusses how to make API calls, how to use the provided data structures, and how to work the various features of the client library, including media upload and download, error handling, retries, pagination, and logging.
* The [Auth Guide](https://github.com/googleapis/google-api-ruby-client/blob/master/docs/auth-guide.md) discusses authentication in the client libraries, including API keys, OAuth 2.0, service accounts, and environment variables.
(Note: the above documents are written for the legacy clients in general, and their examples may not reflect the Admin service in particular.)
(Note: the above documents are written for the simple REST clients in general, and their examples may not reflect the Admin service in particular.)
For reference information on specific calls in the Admin SDK API, see the {Google::Apis::AdminDatatransferV1::DataTransferService class reference docs}.
## Which client should I use?
Google provides two types of Ruby API client libraries: **legacy REST clients** and **modern clients**.
Google provides two types of Ruby API client libraries: **simple REST clients** and **modern clients**.
This library, `google-apis-admin_datatransfer_v1`, is a legacy REST client. You can identify legacy clients by their gem names, which are always in the form `google-apis-<servicename>_<serviceversion>`. The legacy REST clients connect to HTTP/JSON REST endpoints and are automatically generated from service discovery documents. They support most API functionality, but their class interfaces are sometimes awkward.
This library, `google-apis-admin_datatransfer_v1`, is a simple REST client. You can identify these clients by their gem names, which are always in the form `google-apis-<servicename>_<serviceversion>`. The simple REST clients connect to HTTP/JSON REST endpoints and are automatically generated from service discovery documents. They support most API functionality, but their class interfaces are sometimes awkward.
Modern clients are produced by a modern code generator, combined with hand-crafted functionality for some services. Most modern clients connect to high-performance gRPC endpoints, although a few are backed by REST services. Modern clients are available for many Google services, especially Cloud Platform services, but do not yet support all the services covered by the legacy clients.
Modern clients are produced by a modern code generator, sometimes combined with hand-crafted functionality. Most modern clients connect to high-performance gRPC endpoints, although a few are backed by REST services. Modern clients are available for many Google services, especially Google Cloud Platform services, but do not yet support all the services covered by the simple clients.
Gem names for modern clients are often of the form `google-cloud-<service_name>`. (For example, [google-cloud-pubsub](https://rubygems.org/gems/google-cloud-pubsub).) Note that most modern clients also have corresponding "versioned" gems with names like `google-cloud-<service_name>-<version>`. (For example, [google-cloud-pubsub-v1](https://rubygems.org/gems/google-cloud-pubsub-v1).) The "versioned" gems can be used directly, but often provide lower-level interfaces. In most cases, the main gem is recommended.
**For most users, we recommend the modern client, if one is available.** Compared with legacy clients, modern clients are generally much easier to use and more Ruby-like, support more advanced features such as streaming and long-running operations, and often provide much better performance. You may consider using a legacy client instead, if a modern client is not yet available for the service you want to use, or if you are not able to use gRPC on your infrastructure.
**For most users, we recommend the modern client, if one is available.** Compared with simple clients, modern clients are generally much easier to use and more Ruby-like, support more advanced features such as streaming and long-running operations, and often provide much better performance. You may consider using a simple client instead, if a modern client is not yet available for the service you want to use, or if you are not able to use gRPC on your infrastructure.
The [product documentation](http://developers.google.com/admin-sdk/) may provide guidance regarding the preferred client library to use.

6
generated/google-apis-admin_datatransfer_v1/google-apis-admin_datatransfer_v1.gemspec
View File

@ -5,10 +5,10 @@ Gem::Specification.new do |gem|
gem.version = Google::Apis::AdminDatatransferV1::GEM_VERSION
gem.authors = ["Google LLC"]
gem.email = "googleapis-packages@google.com"
gem.summary = "Legacy REST client for Admin SDK API DatatransferV1"
gem.summary = "Simple REST client for Admin SDK API DatatransferV1"
gem.description =
"This is the legacy REST client for Admin SDK API DatatransferV1." \
" Legacy REST clients are simple Ruby libraries that provide access to" \
"This is the simple REST client for Admin SDK API DatatransferV1." \
" Simple REST clients are Ruby client libraries that provide access to" \
" Google services via their HTTP REST API endpoints. These libraries are" \
" generated and updated automatically based on the discovery documents" \
" published by the service, and they handle most concerns such as" \

16
generated/google-apis-admin_directory_v1/OVERVIEW.md
View File

@ -1,4 +1,4 @@
# Legacy REST client for version DirectoryV1 of the Admin SDK API
# Simple REST client for version DirectoryV1 of the Admin SDK API
This is a simple client library for version DirectoryV1 of the Admin SDK API. It provides:
@ -7,7 +7,7 @@ This is a simple client library for version DirectoryV1 of the Admin SDK API. It
* Integration with the googleauth gem for authentication using OAuth, API keys, and service accounts.
* Control of retry, pagination, and timeouts.
Note that although this client library is supported and will continue to be updated to track changes to the service, it is considered legacy. A more modern client may be available for many Google services, especially Cloud Platform services. See the section below titled *Which client should I use?* for more information.
Note that although this client library is supported and will continue to be updated to track changes to the service, it is otherwise considered complete and not under active development. Many Google services, especially Google Cloud Platform services, may provide a more modern client that is under more active development and improvement. See the section below titled *Which client should I use?* for more information.
## Getting started
@ -58,26 +58,26 @@ See the class reference docs for information on the methods you can call from a
## Documentation
More detailed descriptions of the Google legacy REST clients are available in two documents.
More detailed descriptions of the Google simple REST clients are available in two documents.
* The [Usage Guide](https://github.com/googleapis/google-api-ruby-client/blob/master/docs/usage-guide.md) discusses how to make API calls, how to use the provided data structures, and how to work the various features of the client library, including media upload and download, error handling, retries, pagination, and logging.
* The [Auth Guide](https://github.com/googleapis/google-api-ruby-client/blob/master/docs/auth-guide.md) discusses authentication in the client libraries, including API keys, OAuth 2.0, service accounts, and environment variables.
(Note: the above documents are written for the legacy clients in general, and their examples may not reflect the Admin service in particular.)
(Note: the above documents are written for the simple REST clients in general, and their examples may not reflect the Admin service in particular.)
For reference information on specific calls in the Admin SDK API, see the {Google::Apis::AdminDirectoryV1::DirectoryService class reference docs}.
## Which client should I use?
Google provides two types of Ruby API client libraries: **legacy REST clients** and **modern clients**.
Google provides two types of Ruby API client libraries: **simple REST clients** and **modern clients**.
This library, `google-apis-admin_directory_v1`, is a legacy REST client. You can identify legacy clients by their gem names, which are always in the form `google-apis-<servicename>_<serviceversion>`. The legacy REST clients connect to HTTP/JSON REST endpoints and are automatically generated from service discovery documents. They support most API functionality, but their class interfaces are sometimes awkward.
This library, `google-apis-admin_directory_v1`, is a simple REST client. You can identify these clients by their gem names, which are always in the form `google-apis-<servicename>_<serviceversion>`. The simple REST clients connect to HTTP/JSON REST endpoints and are automatically generated from service discovery documents. They support most API functionality, but their class interfaces are sometimes awkward.
Modern clients are produced by a modern code generator, combined with hand-crafted functionality for some services. Most modern clients connect to high-performance gRPC endpoints, although a few are backed by REST services. Modern clients are available for many Google services, especially Cloud Platform services, but do not yet support all the services covered by the legacy clients.
Modern clients are produced by a modern code generator, sometimes combined with hand-crafted functionality. Most modern clients connect to high-performance gRPC endpoints, although a few are backed by REST services. Modern clients are available for many Google services, especially Google Cloud Platform services, but do not yet support all the services covered by the simple clients.
Gem names for modern clients are often of the form `google-cloud-<service_name>`. (For example, [google-cloud-pubsub](https://rubygems.org/gems/google-cloud-pubsub).) Note that most modern clients also have corresponding "versioned" gems with names like `google-cloud-<service_name>-<version>`. (For example, [google-cloud-pubsub-v1](https://rubygems.org/gems/google-cloud-pubsub-v1).) The "versioned" gems can be used directly, but often provide lower-level interfaces. In most cases, the main gem is recommended.
**For most users, we recommend the modern client, if one is available.** Compared with legacy clients, modern clients are generally much easier to use and more Ruby-like, support more advanced features such as streaming and long-running operations, and often provide much better performance. You may consider using a legacy client instead, if a modern client is not yet available for the service you want to use, or if you are not able to use gRPC on your infrastructure.
**For most users, we recommend the modern client, if one is available.** Compared with simple clients, modern clients are generally much easier to use and more Ruby-like, support more advanced features such as streaming and long-running operations, and often provide much better performance. You may consider using a simple client instead, if a modern client is not yet available for the service you want to use, or if you are not able to use gRPC on your infrastructure.
The [product documentation](http://developers.google.com/admin-sdk/) may provide guidance regarding the preferred client library to use.

6
generated/google-apis-admin_directory_v1/google-apis-admin_directory_v1.gemspec
View File

@ -5,10 +5,10 @@ Gem::Specification.new do |gem|
gem.version = Google::Apis::AdminDirectoryV1::GEM_VERSION
gem.authors = ["Google LLC"]
gem.email = "googleapis-packages@google.com"
gem.summary = "Legacy REST client for Admin SDK API DirectoryV1"
gem.summary = "Simple REST client for Admin SDK API DirectoryV1"
gem.description =
"This is the legacy REST client for Admin SDK API DirectoryV1." \
" Legacy REST clients are simple Ruby libraries that provide access to" \
"This is the simple REST client for Admin SDK API DirectoryV1." \
" Simple REST clients are Ruby client libraries that provide access to" \
" Google services via their HTTP REST API endpoints. These libraries are" \
" generated and updated automatically based on the discovery documents" \
" published by the service, and they handle most concerns such as" \

4
generated/google-apis-admin_reports_v1/CHANGELOG.md
View File

@ -1,7 +1,7 @@
# Release history for google-apis-admin_reports_v1
### v0.1.0 (2021-01-01)
### v0.1.0 (2021-01-07)
* Regenerated using generator version 0.1.1
* Regenerated from discovery document revision 20201208
* Regenerated using generator version 0.1.0

16
generated/google-apis-admin_reports_v1/OVERVIEW.md
View File

@ -1,4 +1,4 @@
# Legacy REST client for version ReportsV1 of the Admin SDK API
# Simple REST client for version ReportsV1 of the Admin SDK API
This is a simple client library for version ReportsV1 of the Admin SDK API. It provides:
@ -7,7 +7,7 @@ This is a simple client library for version ReportsV1 of the Admin SDK API. It p
* Integration with the googleauth gem for authentication using OAuth, API keys, and service accounts.
* Control of retry, pagination, and timeouts.
Note that although this client library is supported and will continue to be updated to track changes to the service, it is considered legacy. A more modern client may be available for many Google services, especially Cloud Platform services. See the section below titled *Which client should I use?* for more information.
Note that although this client library is supported and will continue to be updated to track changes to the service, it is otherwise considered complete and not under active development. Many Google services, especially Google Cloud Platform services, may provide a more modern client that is under more active development and improvement. See the section below titled *Which client should I use?* for more information.
## Getting started
@ -58,26 +58,26 @@ See the class reference docs for information on the methods you can call from a
## Documentation
More detailed descriptions of the Google legacy REST clients are available in two documents.
More detailed descriptions of the Google simple REST clients are available in two documents.
* The [Usage Guide](https://github.com/googleapis/google-api-ruby-client/blob/master/docs/usage-guide.md) discusses how to make API calls, how to use the provided data structures, and how to work the various features of the client library, including media upload and download, error handling, retries, pagination, and logging.
* The [Auth Guide](https://github.com/googleapis/google-api-ruby-client/blob/master/docs/auth-guide.md) discusses authentication in the client libraries, including API keys, OAuth 2.0, service accounts, and environment variables.
(Note: the above documents are written for the legacy clients in general, and their examples may not reflect the Admin service in particular.)
(Note: the above documents are written for the simple REST clients in general, and their examples may not reflect the Admin service in particular.)
For reference information on specific calls in the Admin SDK API, see the {Google::Apis::AdminReportsV1::ReportsService class reference docs}.
## Which client should I use?
Google provides two types of Ruby API client libraries: **legacy REST clients** and **modern clients**.
Google provides two types of Ruby API client libraries: **simple REST clients** and **modern clients**.
This library, `google-apis-admin_reports_v1`, is a legacy REST client. You can identify legacy clients by their gem names, which are always in the form `google-apis-<servicename>_<serviceversion>`. The legacy REST clients connect to HTTP/JSON REST endpoints and are automatically generated from service discovery documents. They support most API functionality, but their class interfaces are sometimes awkward.
This library, `google-apis-admin_reports_v1`, is a simple REST client. You can identify these clients by their gem names, which are always in the form `google-apis-<servicename>_<serviceversion>`. The simple REST clients connect to HTTP/JSON REST endpoints and are automatically generated from service discovery documents. They support most API functionality, but their class interfaces are sometimes awkward.
Modern clients are produced by a modern code generator, combined with hand-crafted functionality for some services. Most modern clients connect to high-performance gRPC endpoints, although a few are backed by REST services. Modern clients are available for many Google services, especially Cloud Platform services, but do not yet support all the services covered by the legacy clients.
Modern clients are produced by a modern code generator, sometimes combined with hand-crafted functionality. Most modern clients connect to high-performance gRPC endpoints, although a few are backed by REST services. Modern clients are available for many Google services, especially Google Cloud Platform services, but do not yet support all the services covered by the simple clients.
Gem names for modern clients are often of the form `google-cloud-<service_name>`. (For example, [google-cloud-pubsub](https://rubygems.org/gems/google-cloud-pubsub).) Note that most modern clients also have corresponding "versioned" gems with names like `google-cloud-<service_name>-<version>`. (For example, [google-cloud-pubsub-v1](https://rubygems.org/gems/google-cloud-pubsub-v1).) The "versioned" gems can be used directly, but often provide lower-level interfaces. In most cases, the main gem is recommended.
**For most users, we recommend the modern client, if one is available.** Compared with legacy clients, modern clients are generally much easier to use and more Ruby-like, support more advanced features such as streaming and long-running operations, and often provide much better performance. You may consider using a legacy client instead, if a modern client is not yet available for the service you want to use, or if you are not able to use gRPC on your infrastructure.
**For most users, we recommend the modern client, if one is available.** Compared with simple clients, modern clients are generally much easier to use and more Ruby-like, support more advanced features such as streaming and long-running operations, and often provide much better performance. You may consider using a simple client instead, if a modern client is not yet available for the service you want to use, or if you are not able to use gRPC on your infrastructure.
The [product documentation](http://developers.google.com/admin-sdk/) may provide guidance regarding the preferred client library to use.

6
generated/google-apis-admin_reports_v1/google-apis-admin_reports_v1.gemspec
View File

@ -5,10 +5,10 @@ Gem::Specification.new do |gem|
gem.version = Google::Apis::AdminReportsV1::GEM_VERSION
gem.authors = ["Google LLC"]
gem.email = "googleapis-packages@google.com"
gem.summary = "Legacy REST client for Admin SDK API ReportsV1"
gem.summary = "Simple REST client for Admin SDK API ReportsV1"
gem.description =
"This is the legacy REST client for Admin SDK API ReportsV1." \
" Legacy REST clients are simple Ruby libraries that provide access to" \
"This is the simple REST client for Admin SDK API ReportsV1." \
" Simple REST clients are Ruby client libraries that provide access to" \
" Google services via their HTTP REST API endpoints. These libraries are" \
" generated and updated automatically based on the discovery documents" \
" published by the service, and they handle most concerns such as" \

2
generated/google-apis-admin_reports_v1/lib/google/apis/admin_reports_v1/gem_version.rb
View File

@ -19,7 +19,7 @@ module Google
GEM_VERSION = "0.1.0"
# Version of the code generator used to generate this client
GENERATOR_VERSION = "0.1.0"
GENERATOR_VERSION = "0.1.1"
# Revision of the discovery document this client was generated from
REVISION = "20201208"

16
generated/google-apis-admob_v1/OVERVIEW.md
View File

@ -1,4 +1,4 @@
# Legacy REST client for version V1 of the AdMob API
# Simple REST client for version V1 of the AdMob API
This is a simple client library for version V1 of the AdMob API. It provides:
@ -7,7 +7,7 @@ This is a simple client library for version V1 of the AdMob API. It provides:
* Integration with the googleauth gem for authentication using OAuth, API keys, and service accounts.
* Control of retry, pagination, and timeouts.
Note that although this client library is supported and will continue to be updated to track changes to the service, it is considered legacy. A more modern client may be available for many Google services, especially Cloud Platform services. See the section below titled *Which client should I use?* for more information.
Note that although this client library is supported and will continue to be updated to track changes to the service, it is otherwise considered complete and not under active development. Many Google services, especially Google Cloud Platform services, may provide a more modern client that is under more active development and improvement. See the section below titled *Which client should I use?* for more information.
## Getting started
@ -58,26 +58,26 @@ See the class reference docs for information on the methods you can call from a
## Documentation
More detailed descriptions of the Google legacy REST clients are available in two documents.
More detailed descriptions of the Google simple REST clients are available in two documents.
* The [Usage Guide](https://github.com/googleapis/google-api-ruby-client/blob/master/docs/usage-guide.md) discusses how to make API calls, how to use the provided data structures, and how to work the various features of the client library, including media upload and download, error handling, retries, pagination, and logging.
* The [Auth Guide](https://github.com/googleapis/google-api-ruby-client/blob/master/docs/auth-guide.md) discusses authentication in the client libraries, including API keys, OAuth 2.0, service accounts, and environment variables.
(Note: the above documents are written for the legacy clients in general, and their examples may not reflect the Admob service in particular.)
(Note: the above documents are written for the simple REST clients in general, and their examples may not reflect the Admob service in particular.)
For reference information on specific calls in the AdMob API, see the {Google::Apis::AdmobV1::AdMobService class reference docs}.
## Which client should I use?
Google provides two types of Ruby API client libraries: **legacy REST clients** and **modern clients**.
Google provides two types of Ruby API client libraries: **simple REST clients** and **modern clients**.
This library, `google-apis-admob_v1`, is a legacy REST client. You can identify legacy clients by their gem names, which are always in the form `google-apis-<servicename>_<serviceversion>`. The legacy REST clients connect to HTTP/JSON REST endpoints and are automatically generated from service discovery documents. They support most API functionality, but their class interfaces are sometimes awkward.
This library, `google-apis-admob_v1`, is a simple REST client. You can identify these clients by their gem names, which are always in the form `google-apis-<servicename>_<serviceversion>`. The simple REST clients connect to HTTP/JSON REST endpoints and are automatically generated from service discovery documents. They support most API functionality, but their class interfaces are sometimes awkward.
Modern clients are produced by a modern code generator, combined with hand-crafted functionality for some services. Most modern clients connect to high-performance gRPC endpoints, although a few are backed by REST services. Modern clients are available for many Google services, especially Cloud Platform services, but do not yet support all the services covered by the legacy clients.
Modern clients are produced by a modern code generator, sometimes combined with hand-crafted functionality. Most modern clients connect to high-performance gRPC endpoints, although a few are backed by REST services. Modern clients are available for many Google services, especially Google Cloud Platform services, but do not yet support all the services covered by the simple clients.
Gem names for modern clients are often of the form `google-cloud-<service_name>`. (For example, [google-cloud-pubsub](https://rubygems.org/gems/google-cloud-pubsub).) Note that most modern clients also have corresponding "versioned" gems with names like `google-cloud-<service_name>-<version>`. (For example, [google-cloud-pubsub-v1](https://rubygems.org/gems/google-cloud-pubsub-v1).) The "versioned" gems can be used directly, but often provide lower-level interfaces. In most cases, the main gem is recommended.
**For most users, we recommend the modern client, if one is available.** Compared with legacy clients, modern clients are generally much easier to use and more Ruby-like, support more advanced features such as streaming and long-running operations, and often provide much better performance. You may consider using a legacy client instead, if a modern client is not yet available for the service you want to use, or if you are not able to use gRPC on your infrastructure.
**For most users, we recommend the modern client, if one is available.** Compared with simple clients, modern clients are generally much easier to use and more Ruby-like, support more advanced features such as streaming and long-running operations, and often provide much better performance. You may consider using a simple client instead, if a modern client is not yet available for the service you want to use, or if you are not able to use gRPC on your infrastructure.
The [product documentation](https://developers.google.com/admob/api/) may provide guidance regarding the preferred client library to use.

6
generated/google-apis-admob_v1/google-apis-admob_v1.gemspec
View File

@ -5,10 +5,10 @@ Gem::Specification.new do |gem|
gem.version = Google::Apis::AdmobV1::GEM_VERSION
gem.authors = ["Google LLC"]
gem.email = "googleapis-packages@google.com"
gem.summary = "Legacy REST client for AdMob API V1"
gem.summary = "Simple REST client for AdMob API V1"
gem.description =
"This is the legacy REST client for AdMob API V1." \
" Legacy REST clients are simple Ruby libraries that provide access to" \
"This is the simple REST client for AdMob API V1." \
" Simple REST clients are Ruby client libraries that provide access to" \
" Google services via their HTTP REST API endpoints. These libraries are" \
" generated and updated automatically based on the discovery documents" \
" published by the service, and they handle most concerns such as" \

16
generated/google-apis-admob_v1beta/OVERVIEW.md
View File

@ -1,4 +1,4 @@
# Legacy REST client for version V1beta of the AdMob API
# Simple REST client for version V1beta of the AdMob API
This is a simple client library for version V1beta of the AdMob API. It provides:
@ -7,7 +7,7 @@ This is a simple client library for version V1beta of the AdMob API. It provides
* Integration with the googleauth gem for authentication using OAuth, API keys, and service accounts.
* Control of retry, pagination, and timeouts.
Note that although this client library is supported and will continue to be updated to track changes to the service, it is considered legacy. A more modern client may be available for many Google services, especially Cloud Platform services. See the section below titled *Which client should I use?* for more information.
Note that although this client library is supported and will continue to be updated to track changes to the service, it is otherwise considered complete and not under active development. Many Google services, especially Google Cloud Platform services, may provide a more modern client that is under more active development and improvement. See the section below titled *Which client should I use?* for more information.
## Getting started
@ -58,26 +58,26 @@ See the class reference docs for information on the methods you can call from a
## Documentation
More detailed descriptions of the Google legacy REST clients are available in two documents.
More detailed descriptions of the Google simple REST clients are available in two documents.
* The [Usage Guide](https://github.com/googleapis/google-api-ruby-client/blob/master/docs/usage-guide.md) discusses how to make API calls, how to use the provided data structures, and how to work the various features of the client library, including media upload and download, error handling, retries, pagination, and logging.
* The [Auth Guide](https://github.com/googleapis/google-api-ruby-client/blob/master/docs/auth-guide.md) discusses authentication in the client libraries, including API keys, OAuth 2.0, service accounts, and environment variables.
(Note: the above documents are written for the legacy clients in general, and their examples may not reflect the Admob service in particular.)
(Note: the above documents are written for the simple REST clients in general, and their examples may not reflect the Admob service in particular.)
For reference information on specific calls in the AdMob API, see the {Google::Apis::AdmobV1beta::AdMobService class reference docs}.
## Which client should I use?
Google provides two types of Ruby API client libraries: **legacy REST clients** and **modern clients**.
Google provides two types of Ruby API client libraries: **simple REST clients** and **modern clients**.
This library, `google-apis-admob_v1beta`, is a legacy REST client. You can identify legacy clients by their gem names, which are always in the form `google-apis-<servicename>_<serviceversion>`. The legacy REST clients connect to HTTP/JSON REST endpoints and are automatically generated from service discovery documents. They support most API functionality, but their class interfaces are sometimes awkward.
This library, `google-apis-admob_v1beta`, is a simple REST client. You can identify these clients by their gem names, which are always in the form `google-apis-<servicename>_<serviceversion>`. The simple REST clients connect to HTTP/JSON REST endpoints and are automatically generated from service discovery documents. They support most API functionality, but their class interfaces are sometimes awkward.
Modern clients are produced by a modern code generator, combined with hand-crafted functionality for some services. Most modern clients connect to high-performance gRPC endpoints, although a few are backed by REST services. Modern clients are available for many Google services, especially Cloud Platform services, but do not yet support all the services covered by the legacy clients.
Modern clients are produced by a modern code generator, sometimes combined with hand-crafted functionality. Most modern clients connect to high-performance gRPC endpoints, although a few are backed by REST services. Modern clients are available for many Google services, especially Google Cloud Platform services, but do not yet support all the services covered by the simple clients.
Gem names for modern clients are often of the form `google-cloud-<service_name>`. (For example, [google-cloud-pubsub](https://rubygems.org/gems/google-cloud-pubsub).) Note that most modern clients also have corresponding "versioned" gems with names like `google-cloud-<service_name>-<version>`. (For example, [google-cloud-pubsub-v1](https://rubygems.org/gems/google-cloud-pubsub-v1).) The "versioned" gems can be used directly, but often provide lower-level interfaces. In most cases, the main gem is recommended.
**For most users, we recommend the modern client, if one is available.** Compared with legacy clients, modern clients are generally much easier to use and more Ruby-like, support more advanced features such as streaming and long-running operations, and often provide much better performance. You may consider using a legacy client instead, if a modern client is not yet available for the service you want to use, or if you are not able to use gRPC on your infrastructure.
**For most users, we recommend the modern client, if one is available.** Compared with simple clients, modern clients are generally much easier to use and more Ruby-like, support more advanced features such as streaming and long-running operations, and often provide much better performance. You may consider using a simple client instead, if a modern client is not yet available for the service you want to use, or if you are not able to use gRPC on your infrastructure.
The [product documentation](https://developers.google.com/admob/api/) may provide guidance regarding the preferred client library to use.

6
generated/google-apis-admob_v1beta/google-apis-admob_v1beta.gemspec
View File

@ -5,10 +5,10 @@ Gem::Specification.new do |gem|
gem.version = Google::Apis::AdmobV1beta::GEM_VERSION
gem.authors = ["Google LLC"]
gem.email = "googleapis-packages@google.com"
gem.summary = "Legacy REST client for AdMob API V1beta"
gem.summary = "Simple REST client for AdMob API V1beta"
gem.description =
"This is the legacy REST client for AdMob API V1beta." \
" Legacy REST clients are simple Ruby libraries that provide access to" \
"This is the simple REST client for AdMob API V1beta." \
" Simple REST clients are Ruby client libraries that provide access to" \
" Google services via their HTTP REST API endpoints. These libraries are" \
" generated and updated automatically based on the discovery documents" \
" published by the service, and they handle most concerns such as" \

4
generated/google-apis-adsense_v1_4/CHANGELOG.md
View File

@ -1,7 +1,7 @@
# Release history for google-apis-adsense_v1_4
### v0.1.0 (2021-01-01)
### v0.1.0 (2021-01-07)
* Regenerated using generator version 0.1.1
* Regenerated from discovery document revision 20201002
* Regenerated using generator version 0.1.0

16
generated/google-apis-adsense_v1_4/OVERVIEW.md
View File

@ -1,4 +1,4 @@
# Legacy REST client for version V1_4 of the AdSense Management API
# Simple REST client for version V1_4 of the AdSense Management API
This is a simple client library for version V1_4 of the AdSense Management API. It provides:
@ -7,7 +7,7 @@ This is a simple client library for version V1_4 of the AdSense Management API.
* Integration with the googleauth gem for authentication using OAuth, API keys, and service accounts.
* Control of retry, pagination, and timeouts.
Note that although this client library is supported and will continue to be updated to track changes to the service, it is considered legacy. A more modern client may be available for many Google services, especially Cloud Platform services. See the section below titled *Which client should I use?* for more information.
Note that although this client library is supported and will continue to be updated to track changes to the service, it is otherwise considered complete and not under active development. Many Google services, especially Google Cloud Platform services, may provide a more modern client that is under more active development and improvement. See the section below titled *Which client should I use?* for more information.
## Getting started
@ -58,26 +58,26 @@ See the class reference docs for information on the methods you can call from a
## Documentation
More detailed descriptions of the Google legacy REST clients are available in two documents.
More detailed descriptions of the Google simple REST clients are available in two documents.
* The [Usage Guide](https://github.com/googleapis/google-api-ruby-client/blob/master/docs/usage-guide.md) discusses how to make API calls, how to use the provided data structures, and how to work the various features of the client library, including media upload and download, error handling, retries, pagination, and logging.
* The [Auth Guide](https://github.com/googleapis/google-api-ruby-client/blob/master/docs/auth-guide.md) discusses authentication in the client libraries, including API keys, OAuth 2.0, service accounts, and environment variables.
(Note: the above documents are written for the legacy clients in general, and their examples may not reflect the Adsense service in particular.)
(Note: the above documents are written for the simple REST clients in general, and their examples may not reflect the Adsense service in particular.)
For reference information on specific calls in the AdSense Management API, see the {Google::Apis::AdsenseV1_4::AdSenseService class reference docs}.
## Which client should I use?
Google provides two types of Ruby API client libraries: **legacy REST clients** and **modern clients**.
Google provides two types of Ruby API client libraries: **simple REST clients** and **modern clients**.
This library, `google-apis-adsense_v1_4`, is a legacy REST client. You can identify legacy clients by their gem names, which are always in the form `google-apis-<servicename>_<serviceversion>`. The legacy REST clients connect to HTTP/JSON REST endpoints and are automatically generated from service discovery documents. They support most API functionality, but their class interfaces are sometimes awkward.
This library, `google-apis-adsense_v1_4`, is a simple REST client. You can identify these clients by their gem names, which are always in the form `google-apis-<servicename>_<serviceversion>`. The simple REST clients connect to HTTP/JSON REST endpoints and are automatically generated from service discovery documents. They support most API functionality, but their class interfaces are sometimes awkward.
Modern clients are produced by a modern code generator, combined with hand-crafted functionality for some services. Most modern clients connect to high-performance gRPC endpoints, although a few are backed by REST services. Modern clients are available for many Google services, especially Cloud Platform services, but do not yet support all the services covered by the legacy clients.
Modern clients are produced by a modern code generator, sometimes combined with hand-crafted functionality. Most modern clients connect to high-performance gRPC endpoints, although a few are backed by REST services. Modern clients are available for many Google services, especially Google Cloud Platform services, but do not yet support all the services covered by the simple clients.
Gem names for modern clients are often of the form `google-cloud-<service_name>`. (For example, [google-cloud-pubsub](https://rubygems.org/gems/google-cloud-pubsub).) Note that most modern clients also have corresponding "versioned" gems with names like `google-cloud-<service_name>-<version>`. (For example, [google-cloud-pubsub-v1](https://rubygems.org/gems/google-cloud-pubsub-v1).) The "versioned" gems can be used directly, but often provide lower-level interfaces. In most cases, the main gem is recommended.
**For most users, we recommend the modern client, if one is available.** Compared with legacy clients, modern clients are generally much easier to use and more Ruby-like, support more advanced features such as streaming and long-running operations, and often provide much better performance. You may consider using a legacy client instead, if a modern client is not yet available for the service you want to use, or if you are not able to use gRPC on your infrastructure.
**For most users, we recommend the modern client, if one is available.** Compared with simple clients, modern clients are generally much easier to use and more Ruby-like, support more advanced features such as streaming and long-running operations, and often provide much better performance. You may consider using a simple client instead, if a modern client is not yet available for the service you want to use, or if you are not able to use gRPC on your infrastructure.
The [product documentation](https://developers.google.com/adsense/management/) may provide guidance regarding the preferred client library to use.

6
generated/google-apis-adsense_v1_4/google-apis-adsense_v1_4.gemspec
View File

@ -5,10 +5,10 @@ Gem::Specification.new do |gem|
gem.version = Google::Apis::AdsenseV1_4::GEM_VERSION
gem.authors = ["Google LLC"]
gem.email = "googleapis-packages@google.com"
gem.summary = "Legacy REST client for AdSense Management API V1_4"
gem.summary = "Simple REST client for AdSense Management API V1_4"
gem.description =
"This is the legacy REST client for AdSense Management API V1_4." \
" Legacy REST clients are simple Ruby libraries that provide access to" \
"This is the simple REST client for AdSense Management API V1_4." \
" Simple REST clients are Ruby client libraries that provide access to" \
" Google services via their HTTP REST API endpoints. These libraries are" \
" generated and updated automatically based on the discovery documents" \
" published by the service, and they handle most concerns such as" \

2
generated/google-apis-adsense_v1_4/lib/google/apis/adsense_v1_4/gem_version.rb
View File

@ -19,7 +19,7 @@ module Google
GEM_VERSION = "0.1.0"
# Version of the code generator used to generate this client
GENERATOR_VERSION = "0.1.0"
GENERATOR_VERSION = "0.1.1"
# Revision of the discovery document this client was generated from
REVISION = "20201002"

4
generated/google-apis-adsensehost_v4_1/CHANGELOG.md
View File

@ -1,7 +1,7 @@
# Release history for google-apis-adsensehost_v4_1
### v0.1.0 (2021-01-01)
### v0.1.0 (2021-01-07)
* Regenerated using generator version 0.1.1
* Regenerated from discovery document revision 20200311
* Regenerated using generator version 0.1.0

16
generated/google-apis-adsensehost_v4_1/OVERVIEW.md
View File

@ -1,4 +1,4 @@
# Legacy REST client for version V4_1 of the AdSense Host API
# Simple REST client for version V4_1 of the AdSense Host API
This is a simple client library for version V4_1 of the AdSense Host API. It provides:
@ -7,7 +7,7 @@ This is a simple client library for version V4_1 of the AdSense Host API. It pro
* Integration with the googleauth gem for authentication using OAuth, API keys, and service accounts.
* Control of retry, pagination, and timeouts.
Note that although this client library is supported and will continue to be updated to track changes to the service, it is considered legacy. A more modern client may be available for many Google services, especially Cloud Platform services. See the section below titled *Which client should I use?* for more information.
Note that although this client library is supported and will continue to be updated to track changes to the service, it is otherwise considered complete and not under active development. Many Google services, especially Google Cloud Platform services, may provide a more modern client that is under more active development and improvement. See the section below titled *Which client should I use?* for more information.
## Getting started
@ -58,26 +58,26 @@ See the class reference docs for information on the methods you can call from a
## Documentation
More detailed descriptions of the Google legacy REST clients are available in two documents.
More detailed descriptions of the Google simple REST clients are available in two documents.
* The [Usage Guide](https://github.com/googleapis/google-api-ruby-client/blob/master/docs/usage-guide.md) discusses how to make API calls, how to use the provided data structures, and how to work the various features of the client library, including media upload and download, error handling, retries, pagination, and logging.
* The [Auth Guide](https://github.com/googleapis/google-api-ruby-client/blob/master/docs/auth-guide.md) discusses authentication in the client libraries, including API keys, OAuth 2.0, service accounts, and environment variables.
(Note: the above documents are written for the legacy clients in general, and their examples may not reflect the Adsensehost service in particular.)
(Note: the above documents are written for the simple REST clients in general, and their examples may not reflect the Adsensehost service in particular.)
For reference information on specific calls in the AdSense Host API, see the {Google::Apis::AdsensehostV4_1::AdSenseHostService class reference docs}.
## Which client should I use?
Google provides two types of Ruby API client libraries: **legacy REST clients** and **modern clients**.
Google provides two types of Ruby API client libraries: **simple REST clients** and **modern clients**.
This library, `google-apis-adsensehost_v4_1`, is a legacy REST client. You can identify legacy clients by their gem names, which are always in the form `google-apis-<servicename>_<serviceversion>`. The legacy REST clients connect to HTTP/JSON REST endpoints and are automatically generated from service discovery documents. They support most API functionality, but their class interfaces are sometimes awkward.
This library, `google-apis-adsensehost_v4_1`, is a simple REST client. You can identify these clients by their gem names, which are always in the form `google-apis-<servicename>_<serviceversion>`. The simple REST clients connect to HTTP/JSON REST endpoints and are automatically generated from service discovery documents. They support most API functionality, but their class interfaces are sometimes awkward.
Modern clients are produced by a modern code generator, combined with hand-crafted functionality for some services. Most modern clients connect to high-performance gRPC endpoints, although a few are backed by REST services. Modern clients are available for many Google services, especially Cloud Platform services, but do not yet support all the services covered by the legacy clients.
Modern clients are produced by a modern code generator, sometimes combined with hand-crafted functionality. Most modern clients connect to high-performance gRPC endpoints, although a few are backed by REST services. Modern clients are available for many Google services, especially Google Cloud Platform services, but do not yet support all the services covered by the simple clients.
Gem names for modern clients are often of the form `google-cloud-<service_name>`. (For example, [google-cloud-pubsub](https://rubygems.org/gems/google-cloud-pubsub).) Note that most modern clients also have corresponding "versioned" gems with names like `google-cloud-<service_name>-<version>`. (For example, [google-cloud-pubsub-v1](https://rubygems.org/gems/google-cloud-pubsub-v1).) The "versioned" gems can be used directly, but often provide lower-level interfaces. In most cases, the main gem is recommended.
**For most users, we recommend the modern client, if one is available.** Compared with legacy clients, modern clients are generally much easier to use and more Ruby-like, support more advanced features such as streaming and long-running operations, and often provide much better performance. You may consider using a legacy client instead, if a modern client is not yet available for the service you want to use, or if you are not able to use gRPC on your infrastructure.
**For most users, we recommend the modern client, if one is available.** Compared with simple clients, modern clients are generally much easier to use and more Ruby-like, support more advanced features such as streaming and long-running operations, and often provide much better performance. You may consider using a simple client instead, if a modern client is not yet available for the service you want to use, or if you are not able to use gRPC on your infrastructure.
The [product documentation](https://developers.google.com/adsense/host/) may provide guidance regarding the preferred client library to use.

6
generated/google-apis-adsensehost_v4_1/google-apis-adsensehost_v4_1.gemspec
View File

@ -5,10 +5,10 @@ Gem::Specification.new do |gem|
gem.version = Google::Apis::AdsensehostV4_1::GEM_VERSION
gem.authors = ["Google LLC"]
gem.email = "googleapis-packages@google.com"
gem.summary = "Legacy REST client for AdSense Host API V4_1"
gem.summary = "Simple REST client for AdSense Host API V4_1"
gem.description =
"This is the legacy REST client for AdSense Host API V4_1." \
" Legacy REST clients are simple Ruby libraries that provide access to" \
"This is the simple REST client for AdSense Host API V4_1." \
" Simple REST clients are Ruby client libraries that provide access to" \
" Google services via their HTTP REST API endpoints. These libraries are" \
" generated and updated automatically based on the discovery documents" \
" published by the service, and they handle most concerns such as" \

2
generated/google-apis-adsensehost_v4_1/lib/google/apis/adsensehost_v4_1/gem_version.rb
View File

@ -19,7 +19,7 @@ module Google
GEM_VERSION = "0.1.0"
# Version of the code generator used to generate this client
GENERATOR_VERSION = "0.1.0"
GENERATOR_VERSION = "0.1.1"
# Revision of the discovery document this client was generated from
REVISION = "20200311"

16
generated/google-apis-alertcenter_v1beta1/OVERVIEW.md
View File

@ -1,4 +1,4 @@
# Legacy REST client for version V1beta1 of the Google Workspace Alert Center API
# Simple REST client for version V1beta1 of the Google Workspace Alert Center API
This is a simple client library for version V1beta1 of the Google Workspace Alert Center API. It provides:
@ -7,7 +7,7 @@ This is a simple client library for version V1beta1 of the Google Workspace Aler
* Integration with the googleauth gem for authentication using OAuth, API keys, and service accounts.
* Control of retry, pagination, and timeouts.
Note that although this client library is supported and will continue to be updated to track changes to the service, it is considered legacy. A more modern client may be available for many Google services, especially Cloud Platform services. See the section below titled *Which client should I use?* for more information.
Note that although this client library is supported and will continue to be updated to track changes to the service, it is otherwise considered complete and not under active development. Many Google services, especially Google Cloud Platform services, may provide a more modern client that is under more active development and improvement. See the section below titled *Which client should I use?* for more information.
## Getting started
@ -58,26 +58,26 @@ See the class reference docs for information on the methods you can call from a
## Documentation
More detailed descriptions of the Google legacy REST clients are available in two documents.
More detailed descriptions of the Google simple REST clients are available in two documents.
* The [Usage Guide](https://github.com/googleapis/google-api-ruby-client/blob/master/docs/usage-guide.md) discusses how to make API calls, how to use the provided data structures, and how to work the various features of the client library, including media upload and download, error handling, retries, pagination, and logging.
* The [Auth Guide](https://github.com/googleapis/google-api-ruby-client/blob/master/docs/auth-guide.md) discusses authentication in the client libraries, including API keys, OAuth 2.0, service accounts, and environment variables.
(Note: the above documents are written for the legacy clients in general, and their examples may not reflect the Alertcenter service in particular.)
(Note: the above documents are written for the simple REST clients in general, and their examples may not reflect the Alertcenter service in particular.)
For reference information on specific calls in the Google Workspace Alert Center API, see the {Google::Apis::AlertcenterV1beta1::AlertCenterService class reference docs}.
## Which client should I use?
Google provides two types of Ruby API client libraries: **legacy REST clients** and **modern clients**.
Google provides two types of Ruby API client libraries: **simple REST clients** and **modern clients**.
This library, `google-apis-alertcenter_v1beta1`, is a legacy REST client. You can identify legacy clients by their gem names, which are always in the form `google-apis-<servicename>_<serviceversion>`. The legacy REST clients connect to HTTP/JSON REST endpoints and are automatically generated from service discovery documents. They support most API functionality, but their class interfaces are sometimes awkward.
This library, `google-apis-alertcenter_v1beta1`, is a simple REST client. You can identify these clients by their gem names, which are always in the form `google-apis-<servicename>_<serviceversion>`. The simple REST clients connect to HTTP/JSON REST endpoints and are automatically generated from service discovery documents. They support most API functionality, but their class interfaces are sometimes awkward.
Modern clients are produced by a modern code generator, combined with hand-crafted functionality for some services. Most modern clients connect to high-performance gRPC endpoints, although a few are backed by REST services. Modern clients are available for many Google services, especially Cloud Platform services, but do not yet support all the services covered by the legacy clients.
Modern clients are produced by a modern code generator, sometimes combined with hand-crafted functionality. Most modern clients connect to high-performance gRPC endpoints, although a few are backed by REST services. Modern clients are available for many Google services, especially Google Cloud Platform services, but do not yet support all the services covered by the simple clients.
Gem names for modern clients are often of the form `google-cloud-<service_name>`. (For example, [google-cloud-pubsub](https://rubygems.org/gems/google-cloud-pubsub).) Note that most modern clients also have corresponding "versioned" gems with names like `google-cloud-<service_name>-<version>`. (For example, [google-cloud-pubsub-v1](https://rubygems.org/gems/google-cloud-pubsub-v1).) The "versioned" gems can be used directly, but often provide lower-level interfaces. In most cases, the main gem is recommended.
**For most users, we recommend the modern client, if one is available.** Compared with legacy clients, modern clients are generally much easier to use and more Ruby-like, support more advanced features such as streaming and long-running operations, and often provide much better performance. You may consider using a legacy client instead, if a modern client is not yet available for the service you want to use, or if you are not able to use gRPC on your infrastructure.
**For most users, we recommend the modern client, if one is available.** Compared with simple clients, modern clients are generally much easier to use and more Ruby-like, support more advanced features such as streaming and long-running operations, and often provide much better performance. You may consider using a simple client instead, if a modern client is not yet available for the service you want to use, or if you are not able to use gRPC on your infrastructure.
The [product documentation](https://developers.google.com/admin-sdk/alertcenter/) may provide guidance regarding the preferred client library to use.

6
generated/google-apis-alertcenter_v1beta1/google-apis-alertcenter_v1beta1.gemspec
View File

@ -5,10 +5,10 @@ Gem::Specification.new do |gem|
gem.version = Google::Apis::AlertcenterV1beta1::GEM_VERSION
gem.authors = ["Google LLC"]
gem.email = "googleapis-packages@google.com"
gem.summary = "Legacy REST client for Google Workspace Alert Center API V1beta1"
gem.summary = "Simple REST client for Google Workspace Alert Center API V1beta1"
gem.description =
"This is the legacy REST client for Google Workspace Alert Center API V1beta1." \
" Legacy REST clients are simple Ruby libraries that provide access to" \
"This is the simple REST client for Google Workspace Alert Center API V1beta1." \
" Simple REST clients are Ruby client libraries that provide access to" \
" Google services via their HTTP REST API endpoints. These libraries are" \
" generated and updated automatically based on the discovery documents" \
" published by the service, and they handle most concerns such as" \

4
generated/google-apis-analytics_v3/CHANGELOG.md
View File

@ -1,7 +1,7 @@
# Release history for google-apis-analytics_v3
### v0.1.0 (2021-01-01)
### v0.1.0 (2021-01-07)
* Regenerated using generator version 0.1.1
* Regenerated from discovery document revision 20190807
* Regenerated using generator version 0.1.0

16
generated/google-apis-analytics_v3/OVERVIEW.md
View File

@ -1,4 +1,4 @@
# Legacy REST client for version V3 of the Google Analytics API
# Simple REST client for version V3 of the Google Analytics API
This is a simple client library for version V3 of the Google Analytics API. It provides:
@ -7,7 +7,7 @@ This is a simple client library for version V3 of the Google Analytics API. It p
* Integration with the googleauth gem for authentication using OAuth, API keys, and service accounts.
* Control of retry, pagination, and timeouts.
Note that although this client library is supported and will continue to be updated to track changes to the service, it is considered legacy. A more modern client may be available for many Google services, especially Cloud Platform services. See the section below titled *Which client should I use?* for more information.
Note that although this client library is supported and will continue to be updated to track changes to the service, it is otherwise considered complete and not under active development. Many Google services, especially Google Cloud Platform services, may provide a more modern client that is under more active development and improvement. See the section below titled *Which client should I use?* for more information.
## Getting started
@ -58,26 +58,26 @@ See the class reference docs for information on the methods you can call from a
## Documentation
More detailed descriptions of the Google legacy REST clients are available in two documents.
More detailed descriptions of the Google simple REST clients are available in two documents.
* The [Usage Guide](https://github.com/googleapis/google-api-ruby-client/blob/master/docs/usage-guide.md) discusses how to make API calls, how to use the provided data structures, and how to work the various features of the client library, including media upload and download, error handling, retries, pagination, and logging.
* The [Auth Guide](https://github.com/googleapis/google-api-ruby-client/blob/master/docs/auth-guide.md) discusses authentication in the client libraries, including API keys, OAuth 2.0, service accounts, and environment variables.
(Note: the above documents are written for the legacy clients in general, and their examples may not reflect the Analytics service in particular.)
(Note: the above documents are written for the simple REST clients in general, and their examples may not reflect the Analytics service in particular.)
For reference information on specific calls in the Google Analytics API, see the {Google::Apis::AnalyticsV3::AnalyticsService class reference docs}.
## Which client should I use?
Google provides two types of Ruby API client libraries: **legacy REST clients** and **modern clients**.
Google provides two types of Ruby API client libraries: **simple REST clients** and **modern clients**.
This library, `google-apis-analytics_v3`, is a legacy REST client. You can identify legacy clients by their gem names, which are always in the form `google-apis-<servicename>_<serviceversion>`. The legacy REST clients connect to HTTP/JSON REST endpoints and are automatically generated from service discovery documents. They support most API functionality, but their class interfaces are sometimes awkward.
This library, `google-apis-analytics_v3`, is a simple REST client. You can identify these clients by their gem names, which are always in the form `google-apis-<servicename>_<serviceversion>`. The simple REST clients connect to HTTP/JSON REST endpoints and are automatically generated from service discovery documents. They support most API functionality, but their class interfaces are sometimes awkward.
Modern clients are produced by a modern code generator, combined with hand-crafted functionality for some services. Most modern clients connect to high-performance gRPC endpoints, although a few are backed by REST services. Modern clients are available for many Google services, especially Cloud Platform services, but do not yet support all the services covered by the legacy clients.
Modern clients are produced by a modern code generator, sometimes combined with hand-crafted functionality. Most modern clients connect to high-performance gRPC endpoints, although a few are backed by REST services. Modern clients are available for many Google services, especially Google Cloud Platform services, but do not yet support all the services covered by the simple clients.
Gem names for modern clients are often of the form `google-cloud-<service_name>`. (For example, [google-cloud-pubsub](https://rubygems.org/gems/google-cloud-pubsub).) Note that most modern clients also have corresponding "versioned" gems with names like `google-cloud-<service_name>-<version>`. (For example, [google-cloud-pubsub-v1](https://rubygems.org/gems/google-cloud-pubsub-v1).) The "versioned" gems can be used directly, but often provide lower-level interfaces. In most cases, the main gem is recommended.
**For most users, we recommend the modern client, if one is available.** Compared with legacy clients, modern clients are generally much easier to use and more Ruby-like, support more advanced features such as streaming and long-running operations, and often provide much better performance. You may consider using a legacy client instead, if a modern client is not yet available for the service you want to use, or if you are not able to use gRPC on your infrastructure.
**For most users, we recommend the modern client, if one is available.** Compared with simple clients, modern clients are generally much easier to use and more Ruby-like, support more advanced features such as streaming and long-running operations, and often provide much better performance. You may consider using a simple client instead, if a modern client is not yet available for the service you want to use, or if you are not able to use gRPC on your infrastructure.
The [product documentation](https://developers.google.com/analytics/) may provide guidance regarding the preferred client library to use.

6
generated/google-apis-analytics_v3/google-apis-analytics_v3.gemspec
View File

@ -5,10 +5,10 @@ Gem::Specification.new do |gem|
gem.version = Google::Apis::AnalyticsV3::GEM_VERSION
gem.authors = ["Google LLC"]
gem.email = "googleapis-packages@google.com"
gem.summary = "Legacy REST client for Google Analytics API V3"
gem.summary = "Simple REST client for Google Analytics API V3"
gem.description =
"This is the legacy REST client for Google Analytics API V3." \
" Legacy REST clients are simple Ruby libraries that provide access to" \
"This is the simple REST client for Google Analytics API V3." \
" Simple REST clients are Ruby client libraries that provide access to" \
" Google services via their HTTP REST API endpoints. These libraries are" \
" generated and updated automatically based on the discovery documents" \
" published by the service, and they handle most concerns such as" \

2
generated/google-apis-analytics_v3/lib/google/apis/analytics_v3/gem_version.rb
View File

@ -19,7 +19,7 @@ module Google
GEM_VERSION = "0.1.0"
# Version of the code generator used to generate this client
GENERATOR_VERSION = "0.1.0"
GENERATOR_VERSION = "0.1.1"
# Revision of the discovery document this client was generated from
REVISION = "20190807"

6
generated/google-apis-analyticsadmin_v1alpha/CHANGELOG.md
View File

@ -1,7 +1,7 @@
# Release history for google-apis-analyticsadmin_v1alpha
### v0.1.0 (2021-01-01)
### v0.1.0 (2021-01-07)
* Regenerated from discovery document revision 20201213
* Regenerated using generator version 0.1.0
* Regenerated from discovery document revision 20210106
* Regenerated using generator version 0.1.1

16
generated/google-apis-analyticsadmin_v1alpha/OVERVIEW.md
View File

@ -1,4 +1,4 @@
# Legacy REST client for version V1alpha of the Google Analytics Admin API
# Simple REST client for version V1alpha of the Google Analytics Admin API
This is a simple client library for version V1alpha of the Google Analytics Admin API. It provides:
@ -7,7 +7,7 @@ This is a simple client library for version V1alpha of the Google Analytics Admi
* Integration with the googleauth gem for authentication using OAuth, API keys, and service accounts.
* Control of retry, pagination, and timeouts.
Note that although this client library is supported and will continue to be updated to track changes to the service, it is considered legacy. A more modern client may be available for many Google services, especially Cloud Platform services. See the section below titled *Which client should I use?* for more information.
Note that although this client library is supported and will continue to be updated to track changes to the service, it is otherwise considered complete and not under active development. Many Google services, especially Google Cloud Platform services, may provide a more modern client that is under more active development and improvement. See the section below titled *Which client should I use?* for more information.
## Getting started
@ -58,26 +58,26 @@ See the class reference docs for information on the methods you can call from a
## Documentation
More detailed descriptions of the Google legacy REST clients are available in two documents.
More detailed descriptions of the Google simple REST clients are available in two documents.
* The [Usage Guide](https://github.com/googleapis/google-api-ruby-client/blob/master/docs/usage-guide.md) discusses how to make API calls, how to use the provided data structures, and how to work the various features of the client library, including media upload and download, error handling, retries, pagination, and logging.
* The [Auth Guide](https://github.com/googleapis/google-api-ruby-client/blob/master/docs/auth-guide.md) discusses authentication in the client libraries, including API keys, OAuth 2.0, service accounts, and environment variables.
(Note: the above documents are written for the legacy clients in general, and their examples may not reflect the Analyticsadmin service in particular.)
(Note: the above documents are written for the simple REST clients in general, and their examples may not reflect the Analyticsadmin service in particular.)
For reference information on specific calls in the Google Analytics Admin API, see the {Google::Apis::AnalyticsadminV1alpha::GoogleAnalyticsAdminService class reference docs}.
## Which client should I use?
Google provides two types of Ruby API client libraries: **legacy REST clients** and **modern clients**.
Google provides two types of Ruby API client libraries: **simple REST clients** and **modern clients**.
This library, `google-apis-analyticsadmin_v1alpha`, is a legacy REST client. You can identify legacy clients by their gem names, which are always in the form `google-apis-<servicename>_<serviceversion>`. The legacy REST clients connect to HTTP/JSON REST endpoints and are automatically generated from service discovery documents. They support most API functionality, but their class interfaces are sometimes awkward.
This library, `google-apis-analyticsadmin_v1alpha`, is a simple REST client. You can identify these clients by their gem names, which are always in the form `google-apis-<servicename>_<serviceversion>`. The simple REST clients connect to HTTP/JSON REST endpoints and are automatically generated from service discovery documents. They support most API functionality, but their class interfaces are sometimes awkward.
Modern clients are produced by a modern code generator, combined with hand-crafted functionality for some services. Most modern clients connect to high-performance gRPC endpoints, although a few are backed by REST services. Modern clients are available for many Google services, especially Cloud Platform services, but do not yet support all the services covered by the legacy clients.
Modern clients are produced by a modern code generator, sometimes combined with hand-crafted functionality. Most modern clients connect to high-performance gRPC endpoints, although a few are backed by REST services. Modern clients are available for many Google services, especially Google Cloud Platform services, but do not yet support all the services covered by the simple clients.
Gem names for modern clients are often of the form `google-cloud-<service_name>`. (For example, [google-cloud-pubsub](https://rubygems.org/gems/google-cloud-pubsub).) Note that most modern clients also have corresponding "versioned" gems with names like `google-cloud-<service_name>-<version>`. (For example, [google-cloud-pubsub-v1](https://rubygems.org/gems/google-cloud-pubsub-v1).) The "versioned" gems can be used directly, but often provide lower-level interfaces. In most cases, the main gem is recommended.
**For most users, we recommend the modern client, if one is available.** Compared with legacy clients, modern clients are generally much easier to use and more Ruby-like, support more advanced features such as streaming and long-running operations, and often provide much better performance. You may consider using a legacy client instead, if a modern client is not yet available for the service you want to use, or if you are not able to use gRPC on your infrastructure.
**For most users, we recommend the modern client, if one is available.** Compared with simple clients, modern clients are generally much easier to use and more Ruby-like, support more advanced features such as streaming and long-running operations, and often provide much better performance. You may consider using a simple client instead, if a modern client is not yet available for the service you want to use, or if you are not able to use gRPC on your infrastructure.
The [product documentation](http://code.google.com/apis/analytics/docs/mgmt/home.html) may provide guidance regarding the preferred client library to use.

6
generated/google-apis-analyticsadmin_v1alpha/google-apis-analyticsadmin_v1alpha.gemspec
View File

@ -5,10 +5,10 @@ Gem::Specification.new do |gem|
gem.version = Google::Apis::AnalyticsadminV1alpha::GEM_VERSION
gem.authors = ["Google LLC"]
gem.email = "googleapis-packages@google.com"
gem.summary = "Legacy REST client for Google Analytics Admin API V1alpha"
gem.summary = "Simple REST client for Google Analytics Admin API V1alpha"
gem.description =
"This is the legacy REST client for Google Analytics Admin API V1alpha." \
" Legacy REST clients are simple Ruby libraries that provide access to" \
"This is the simple REST client for Google Analytics Admin API V1alpha." \
" Simple REST clients are Ruby client libraries that provide access to" \
" Google services via their HTTP REST API endpoints. These libraries are" \
" generated and updated automatically based on the discovery documents" \
" published by the service, and they handle most concerns such as" \

4
generated/google-apis-analyticsadmin_v1alpha/lib/google/apis/analyticsadmin_v1alpha/gem_version.rb
View File

@ -19,10 +19,10 @@ module Google
GEM_VERSION = "0.1.0"
# Version of the code generator used to generate this client
GENERATOR_VERSION = "0.1.0"
GENERATOR_VERSION = "0.1.1"
# Revision of the discovery document this client was generated from
REVISION = "20201213"
REVISION = "20210106"
end
end
end

10
generated/google-apis-analyticsadmin_v1alpha/lib/google/apis/analyticsadmin_v1alpha/service.rb
View File

@ -761,11 +761,11 @@ module Google
# Required. An expression for filtering the results of the request. Fields
# eligible for filtering are: `parent:`(The resource name of the parent account)
# or `firebase_project:`(The id or number of the linked firebase project). Some
# examples of filters: | Filter | Description | |-----------------------------|--
# -----------------------------------------| | parent:accounts/123 | The account
# with account id: 123. | | firebase_project:project-id | The firebase project
# with id: project-id. | | firebase_project:123 | The firebase project with
# number: 123. |
# examples of filters: ``` | Filter | Description | |----------------------------
# -|-------------------------------------------| | parent:accounts/123 | The
# account with account id: 123. | | firebase_project:project-id | The firebase
# project with id: project-id. | | firebase_project:123 | The firebase project
# with number: 123. | ```
# @param [Fixnum] page_size
# The maximum number of resources to return. The service may return fewer than
# this value, even if there are additional pages. If unspecified, at most 50

16
generated/google-apis-analyticsdata_v1alpha/OVERVIEW.md
View File

@ -1,4 +1,4 @@
# Legacy REST client for version V1alpha of the Google Analytics Data API
# Simple REST client for version V1alpha of the Google Analytics Data API
This is a simple client library for version V1alpha of the Google Analytics Data API. It provides:
@ -7,7 +7,7 @@ This is a simple client library for version V1alpha of the Google Analytics Data
* Integration with the googleauth gem for authentication using OAuth, API keys, and service accounts.
* Control of retry, pagination, and timeouts.
Note that although this client library is supported and will continue to be updated to track changes to the service, it is considered legacy. A more modern client may be available for many Google services, especially Cloud Platform services. See the section below titled *Which client should I use?* for more information.
Note that although this client library is supported and will continue to be updated to track changes to the service, it is otherwise considered complete and not under active development. Many Google services, especially Google Cloud Platform services, may provide a more modern client that is under more active development and improvement. See the section below titled *Which client should I use?* for more information.
## Getting started
@ -58,26 +58,26 @@ See the class reference docs for information on the methods you can call from a
## Documentation
More detailed descriptions of the Google legacy REST clients are available in two documents.
More detailed descriptions of the Google simple REST clients are available in two documents.
* The [Usage Guide](https://github.com/googleapis/google-api-ruby-client/blob/master/docs/usage-guide.md) discusses how to make API calls, how to use the provided data structures, and how to work the various features of the client library, including media upload and download, error handling, retries, pagination, and logging.
* The [Auth Guide](https://github.com/googleapis/google-api-ruby-client/blob/master/docs/auth-guide.md) discusses authentication in the client libraries, including API keys, OAuth 2.0, service accounts, and environment variables.
(Note: the above documents are written for the legacy clients in general, and their examples may not reflect the Analyticsdata service in particular.)
(Note: the above documents are written for the simple REST clients in general, and their examples may not reflect the Analyticsdata service in particular.)
For reference information on specific calls in the Google Analytics Data API, see the {Google::Apis::AnalyticsdataV1alpha::AnalyticsDataService class reference docs}.
## Which client should I use?
Google provides two types of Ruby API client libraries: **legacy REST clients** and **modern clients**.
Google provides two types of Ruby API client libraries: **simple REST clients** and **modern clients**.
This library, `google-apis-analyticsdata_v1alpha`, is a legacy REST client. You can identify legacy clients by their gem names, which are always in the form `google-apis-<servicename>_<serviceversion>`. The legacy REST clients connect to HTTP/JSON REST endpoints and are automatically generated from service discovery documents. They support most API functionality, but their class interfaces are sometimes awkward.
This library, `google-apis-analyticsdata_v1alpha`, is a simple REST client. You can identify these clients by their gem names, which are always in the form `google-apis-<servicename>_<serviceversion>`. The simple REST clients connect to HTTP/JSON REST endpoints and are automatically generated from service discovery documents. They support most API functionality, but their class interfaces are sometimes awkward.
Modern clients are produced by a modern code generator, combined with hand-crafted functionality for some services. Most modern clients connect to high-performance gRPC endpoints, although a few are backed by REST services. Modern clients are available for many Google services, especially Cloud Platform services, but do not yet support all the services covered by the legacy clients.
Modern clients are produced by a modern code generator, sometimes combined with hand-crafted functionality. Most modern clients connect to high-performance gRPC endpoints, although a few are backed by REST services. Modern clients are available for many Google services, especially Google Cloud Platform services, but do not yet support all the services covered by the simple clients.
Gem names for modern clients are often of the form `google-cloud-<service_name>`. (For example, [google-cloud-pubsub](https://rubygems.org/gems/google-cloud-pubsub).) Note that most modern clients also have corresponding "versioned" gems with names like `google-cloud-<service_name>-<version>`. (For example, [google-cloud-pubsub-v1](https://rubygems.org/gems/google-cloud-pubsub-v1).) The "versioned" gems can be used directly, but often provide lower-level interfaces. In most cases, the main gem is recommended.
**For most users, we recommend the modern client, if one is available.** Compared with legacy clients, modern clients are generally much easier to use and more Ruby-like, support more advanced features such as streaming and long-running operations, and often provide much better performance. You may consider using a legacy client instead, if a modern client is not yet available for the service you want to use, or if you are not able to use gRPC on your infrastructure.
**For most users, we recommend the modern client, if one is available.** Compared with simple clients, modern clients are generally much easier to use and more Ruby-like, support more advanced features such as streaming and long-running operations, and often provide much better performance. You may consider using a simple client instead, if a modern client is not yet available for the service you want to use, or if you are not able to use gRPC on your infrastructure.
The [product documentation](https://developers.google.com/analytics/devguides/reporting/data/v1/) may provide guidance regarding the preferred client library to use.

6
generated/google-apis-analyticsdata_v1alpha/google-apis-analyticsdata_v1alpha.gemspec
View File

@ -5,10 +5,10 @@ Gem::Specification.new do |gem|
gem.version = Google::Apis::AnalyticsdataV1alpha::GEM_VERSION
gem.authors = ["Google LLC"]
gem.email = "googleapis-packages@google.com"
gem.summary = "Legacy REST client for Google Analytics Data API V1alpha"
gem.summary = "Simple REST client for Google Analytics Data API V1alpha"
gem.description =
"This is the legacy REST client for Google Analytics Data API V1alpha." \
" Legacy REST clients are simple Ruby libraries that provide access to" \
"This is the simple REST client for Google Analytics Data API V1alpha." \
" Simple REST clients are Ruby client libraries that provide access to" \
" Google services via their HTTP REST API endpoints. These libraries are" \
" generated and updated automatically based on the discovery documents" \
" published by the service, and they handle most concerns such as" \

16
generated/google-apis-analyticsreporting_v4/OVERVIEW.md
View File

@ -1,4 +1,4 @@
# Legacy REST client for version V4 of the Analytics Reporting API
# Simple REST client for version V4 of the Analytics Reporting API
This is a simple client library for version V4 of the Analytics Reporting API. It provides:
@ -7,7 +7,7 @@ This is a simple client library for version V4 of the Analytics Reporting API. I
* Integration with the googleauth gem for authentication using OAuth, API keys, and service accounts.
* Control of retry, pagination, and timeouts.
Note that although this client library is supported and will continue to be updated to track changes to the service, it is considered legacy. A more modern client may be available for many Google services, especially Cloud Platform services. See the section below titled *Which client should I use?* for more information.
Note that although this client library is supported and will continue to be updated to track changes to the service, it is otherwise considered complete and not under active development. Many Google services, especially Google Cloud Platform services, may provide a more modern client that is under more active development and improvement. See the section below titled *Which client should I use?* for more information.
## Getting started
@ -58,26 +58,26 @@ See the class reference docs for information on the methods you can call from a
## Documentation
More detailed descriptions of the Google legacy REST clients are available in two documents.
More detailed descriptions of the Google simple REST clients are available in two documents.
* The [Usage Guide](https://github.com/googleapis/google-api-ruby-client/blob/master/docs/usage-guide.md) discusses how to make API calls, how to use the provided data structures, and how to work the various features of the client library, including media upload and download, error handling, retries, pagination, and logging.
* The [Auth Guide](https://github.com/googleapis/google-api-ruby-client/blob/master/docs/auth-guide.md) discusses authentication in the client libraries, including API keys, OAuth 2.0, service accounts, and environment variables.
(Note: the above documents are written for the legacy clients in general, and their examples may not reflect the Analyticsreporting service in particular.)
(Note: the above documents are written for the simple REST clients in general, and their examples may not reflect the Analyticsreporting service in particular.)
For reference information on specific calls in the Analytics Reporting API, see the {Google::Apis::AnalyticsreportingV4::AnalyticsReportingService class reference docs}.
## Which client should I use?
Google provides two types of Ruby API client libraries: **legacy REST clients** and **modern clients**.
Google provides two types of Ruby API client libraries: **simple REST clients** and **modern clients**.
This library, `google-apis-analyticsreporting_v4`, is a legacy REST client. You can identify legacy clients by their gem names, which are always in the form `google-apis-<servicename>_<serviceversion>`. The legacy REST clients connect to HTTP/JSON REST endpoints and are automatically generated from service discovery documents. They support most API functionality, but their class interfaces are sometimes awkward.
This library, `google-apis-analyticsreporting_v4`, is a simple REST client. You can identify these clients by their gem names, which are always in the form `google-apis-<servicename>_<serviceversion>`. The simple REST clients connect to HTTP/JSON REST endpoints and are automatically generated from service discovery documents. They support most API functionality, but their class interfaces are sometimes awkward.
Modern clients are produced by a modern code generator, combined with hand-crafted functionality for some services. Most modern clients connect to high-performance gRPC endpoints, although a few are backed by REST services. Modern clients are available for many Google services, especially Cloud Platform services, but do not yet support all the services covered by the legacy clients.
Modern clients are produced by a modern code generator, sometimes combined with hand-crafted functionality. Most modern clients connect to high-performance gRPC endpoints, although a few are backed by REST services. Modern clients are available for many Google services, especially Google Cloud Platform services, but do not yet support all the services covered by the simple clients.
Gem names for modern clients are often of the form `google-cloud-<service_name>`. (For example, [google-cloud-pubsub](https://rubygems.org/gems/google-cloud-pubsub).) Note that most modern clients also have corresponding "versioned" gems with names like `google-cloud-<service_name>-<version>`. (For example, [google-cloud-pubsub-v1](https://rubygems.org/gems/google-cloud-pubsub-v1).) The "versioned" gems can be used directly, but often provide lower-level interfaces. In most cases, the main gem is recommended.
**For most users, we recommend the modern client, if one is available.** Compared with legacy clients, modern clients are generally much easier to use and more Ruby-like, support more advanced features such as streaming and long-running operations, and often provide much better performance. You may consider using a legacy client instead, if a modern client is not yet available for the service you want to use, or if you are not able to use gRPC on your infrastructure.
**For most users, we recommend the modern client, if one is available.** Compared with simple clients, modern clients are generally much easier to use and more Ruby-like, support more advanced features such as streaming and long-running operations, and often provide much better performance. You may consider using a simple client instead, if a modern client is not yet available for the service you want to use, or if you are not able to use gRPC on your infrastructure.
The [product documentation](https://developers.google.com/analytics/devguides/reporting/core/v4/) may provide guidance regarding the preferred client library to use.

6
generated/google-apis-analyticsreporting_v4/google-apis-analyticsreporting_v4.gemspec
View File

@ -5,10 +5,10 @@ Gem::Specification.new do |gem|
gem.version = Google::Apis::AnalyticsreportingV4::GEM_VERSION
gem.authors = ["Google LLC"]
gem.email = "googleapis-packages@google.com"
gem.summary = "Legacy REST client for Analytics Reporting API V4"
gem.summary = "Simple REST client for Analytics Reporting API V4"
gem.description =
"This is the legacy REST client for Analytics Reporting API V4." \
" Legacy REST clients are simple Ruby libraries that provide access to" \
"This is the simple REST client for Analytics Reporting API V4." \
" Simple REST clients are Ruby client libraries that provide access to" \
" Google services via their HTTP REST API endpoints. These libraries are" \
" generated and updated automatically based on the discovery documents" \
" published by the service, and they handle most concerns such as" \

4
generated/google-apis-androiddeviceprovisioning_v1/CHANGELOG.md
View File

@ -1,7 +1,7 @@
# Release history for google-apis-androiddeviceprovisioning_v1
### v0.1.0 (2021-01-01)
### v0.1.0 (2021-01-07)
* Regenerated using generator version 0.1.1
* Regenerated from discovery document revision 20200801
* Regenerated using generator version 0.1.0

16
generated/google-apis-androiddeviceprovisioning_v1/OVERVIEW.md
View File

@ -1,4 +1,4 @@
# Legacy REST client for version V1 of the Android Device Provisioning Partner API
# Simple REST client for version V1 of the Android Device Provisioning Partner API
This is a simple client library for version V1 of the Android Device Provisioning Partner API. It provides:
@ -7,7 +7,7 @@ This is a simple client library for version V1 of the Android Device Provisionin
* Integration with the googleauth gem for authentication using OAuth, API keys, and service accounts.
* Control of retry, pagination, and timeouts.
Note that although this client library is supported and will continue to be updated to track changes to the service, it is considered legacy. A more modern client may be available for many Google services, especially Cloud Platform services. See the section below titled *Which client should I use?* for more information.
Note that although this client library is supported and will continue to be updated to track changes to the service, it is otherwise considered complete and not under active development. Many Google services, especially Google Cloud Platform services, may provide a more modern client that is under more active development and improvement. See the section below titled *Which client should I use?* for more information.
## Getting started
@ -58,26 +58,26 @@ See the class reference docs for information on the methods you can call from a
## Documentation
More detailed descriptions of the Google legacy REST clients are available in two documents.
More detailed descriptions of the Google simple REST clients are available in two documents.
* The [Usage Guide](https://github.com/googleapis/google-api-ruby-client/blob/master/docs/usage-guide.md) discusses how to make API calls, how to use the provided data structures, and how to work the various features of the client library, including media upload and download, error handling, retries, pagination, and logging.
* The [Auth Guide](https://github.com/googleapis/google-api-ruby-client/blob/master/docs/auth-guide.md) discusses authentication in the client libraries, including API keys, OAuth 2.0, service accounts, and environment variables.
(Note: the above documents are written for the legacy clients in general, and their examples may not reflect the Androiddeviceprovisioning service in particular.)
(Note: the above documents are written for the simple REST clients in general, and their examples may not reflect the Androiddeviceprovisioning service in particular.)
For reference information on specific calls in the Android Device Provisioning Partner API, see the {Google::Apis::AndroiddeviceprovisioningV1::AndroidProvisioningPartnerService class reference docs}.
## Which client should I use?
Google provides two types of Ruby API client libraries: **legacy REST clients** and **modern clients**.
Google provides two types of Ruby API client libraries: **simple REST clients** and **modern clients**.
This library, `google-apis-androiddeviceprovisioning_v1`, is a legacy REST client. You can identify legacy clients by their gem names, which are always in the form `google-apis-<servicename>_<serviceversion>`. The legacy REST clients connect to HTTP/JSON REST endpoints and are automatically generated from service discovery documents. They support most API functionality, but their class interfaces are sometimes awkward.
This library, `google-apis-androiddeviceprovisioning_v1`, is a simple REST client. You can identify these clients by their gem names, which are always in the form `google-apis-<servicename>_<serviceversion>`. The simple REST clients connect to HTTP/JSON REST endpoints and are automatically generated from service discovery documents. They support most API functionality, but their class interfaces are sometimes awkward.
Modern clients are produced by a modern code generator, combined with hand-crafted functionality for some services. Most modern clients connect to high-performance gRPC endpoints, although a few are backed by REST services. Modern clients are available for many Google services, especially Cloud Platform services, but do not yet support all the services covered by the legacy clients.
Modern clients are produced by a modern code generator, sometimes combined with hand-crafted functionality. Most modern clients connect to high-performance gRPC endpoints, although a few are backed by REST services. Modern clients are available for many Google services, especially Google Cloud Platform services, but do not yet support all the services covered by the simple clients.
Gem names for modern clients are often of the form `google-cloud-<service_name>`. (For example, [google-cloud-pubsub](https://rubygems.org/gems/google-cloud-pubsub).) Note that most modern clients also have corresponding "versioned" gems with names like `google-cloud-<service_name>-<version>`. (For example, [google-cloud-pubsub-v1](https://rubygems.org/gems/google-cloud-pubsub-v1).) The "versioned" gems can be used directly, but often provide lower-level interfaces. In most cases, the main gem is recommended.
**For most users, we recommend the modern client, if one is available.** Compared with legacy clients, modern clients are generally much easier to use and more Ruby-like, support more advanced features such as streaming and long-running operations, and often provide much better performance. You may consider using a legacy client instead, if a modern client is not yet available for the service you want to use, or if you are not able to use gRPC on your infrastructure.
**For most users, we recommend the modern client, if one is available.** Compared with simple clients, modern clients are generally much easier to use and more Ruby-like, support more advanced features such as streaming and long-running operations, and often provide much better performance. You may consider using a simple client instead, if a modern client is not yet available for the service you want to use, or if you are not able to use gRPC on your infrastructure.
The [product documentation](https://developers.google.com/zero-touch/) may provide guidance regarding the preferred client library to use.

6
generated/google-apis-androiddeviceprovisioning_v1/google-apis-androiddeviceprovisioning_v1.gemspec
View File

@ -5,10 +5,10 @@ Gem::Specification.new do |gem|
gem.version = Google::Apis::AndroiddeviceprovisioningV1::GEM_VERSION
gem.authors = ["Google LLC"]
gem.email = "googleapis-packages@google.com"
gem.summary = "Legacy REST client for Android Device Provisioning Partner API V1"
gem.summary = "Simple REST client for Android Device Provisioning Partner API V1"
gem.description =
"This is the legacy REST client for Android Device Provisioning Partner API V1." \
" Legacy REST clients are simple Ruby libraries that provide access to" \
"This is the simple REST client for Android Device Provisioning Partner API V1." \
" Simple REST clients are Ruby client libraries that provide access to" \
" Google services via their HTTP REST API endpoints. These libraries are" \
" generated and updated automatically based on the discovery documents" \
" published by the service, and they handle most concerns such as" \

2
generated/google-apis-androiddeviceprovisioning_v1/lib/google/apis/androiddeviceprovisioning_v1/gem_version.rb
View File

@ -19,7 +19,7 @@ module Google
GEM_VERSION = "0.1.0"
# Version of the code generator used to generate this client
GENERATOR_VERSION = "0.1.0"
GENERATOR_VERSION = "0.1.1"
# Revision of the discovery document this client was generated from
REVISION = "20200801"

4
generated/google-apis-androidenterprise_v1/CHANGELOG.md
View File

@ -1,7 +1,7 @@
# Release history for google-apis-androidenterprise_v1
### v0.1.0 (2021-01-01)
### v0.1.0 (2021-01-07)
* Regenerated using generator version 0.1.1
* Regenerated from discovery document revision 20201125
* Regenerated using generator version 0.1.0

16
generated/google-apis-androidenterprise_v1/OVERVIEW.md
View File

@ -1,4 +1,4 @@
# Legacy REST client for version V1 of the Google Play EMM API
# Simple REST client for version V1 of the Google Play EMM API
This is a simple client library for version V1 of the Google Play EMM API. It provides:
@ -7,7 +7,7 @@ This is a simple client library for version V1 of the Google Play EMM API. It pr
* Integration with the googleauth gem for authentication using OAuth, API keys, and service accounts.
* Control of retry, pagination, and timeouts.
Note that although this client library is supported and will continue to be updated to track changes to the service, it is considered legacy. A more modern client may be available for many Google services, especially Cloud Platform services. See the section below titled *Which client should I use?* for more information.
Note that although this client library is supported and will continue to be updated to track changes to the service, it is otherwise considered complete and not under active development. Many Google services, especially Google Cloud Platform services, may provide a more modern client that is under more active development and improvement. See the section below titled *Which client should I use?* for more information.
## Getting started
@ -58,26 +58,26 @@ See the class reference docs for information on the methods you can call from a
## Documentation
More detailed descriptions of the Google legacy REST clients are available in two documents.
More detailed descriptions of the Google simple REST clients are available in two documents.
* The [Usage Guide](https://github.com/googleapis/google-api-ruby-client/blob/master/docs/usage-guide.md) discusses how to make API calls, how to use the provided data structures, and how to work the various features of the client library, including media upload and download, error handling, retries, pagination, and logging.
* The [Auth Guide](https://github.com/googleapis/google-api-ruby-client/blob/master/docs/auth-guide.md) discusses authentication in the client libraries, including API keys, OAuth 2.0, service accounts, and environment variables.
(Note: the above documents are written for the legacy clients in general, and their examples may not reflect the Androidenterprise service in particular.)
(Note: the above documents are written for the simple REST clients in general, and their examples may not reflect the Androidenterprise service in particular.)
For reference information on specific calls in the Google Play EMM API, see the {Google::Apis::AndroidenterpriseV1::AndroidEnterpriseService class reference docs}.
## Which client should I use?
Google provides two types of Ruby API client libraries: **legacy REST clients** and **modern clients**.
Google provides two types of Ruby API client libraries: **simple REST clients** and **modern clients**.
This library, `google-apis-androidenterprise_v1`, is a legacy REST client. You can identify legacy clients by their gem names, which are always in the form `google-apis-<servicename>_<serviceversion>`. The legacy REST clients connect to HTTP/JSON REST endpoints and are automatically generated from service discovery documents. They support most API functionality, but their class interfaces are sometimes awkward.
This library, `google-apis-androidenterprise_v1`, is a simple REST client. You can identify these clients by their gem names, which are always in the form `google-apis-<servicename>_<serviceversion>`. The simple REST clients connect to HTTP/JSON REST endpoints and are automatically generated from service discovery documents. They support most API functionality, but their class interfaces are sometimes awkward.
Modern clients are produced by a modern code generator, combined with hand-crafted functionality for some services. Most modern clients connect to high-performance gRPC endpoints, although a few are backed by REST services. Modern clients are available for many Google services, especially Cloud Platform services, but do not yet support all the services covered by the legacy clients.
Modern clients are produced by a modern code generator, sometimes combined with hand-crafted functionality. Most modern clients connect to high-performance gRPC endpoints, although a few are backed by REST services. Modern clients are available for many Google services, especially Google Cloud Platform services, but do not yet support all the services covered by the simple clients.
Gem names for modern clients are often of the form `google-cloud-<service_name>`. (For example, [google-cloud-pubsub](https://rubygems.org/gems/google-cloud-pubsub).) Note that most modern clients also have corresponding "versioned" gems with names like `google-cloud-<service_name>-<version>`. (For example, [google-cloud-pubsub-v1](https://rubygems.org/gems/google-cloud-pubsub-v1).) The "versioned" gems can be used directly, but often provide lower-level interfaces. In most cases, the main gem is recommended.
**For most users, we recommend the modern client, if one is available.** Compared with legacy clients, modern clients are generally much easier to use and more Ruby-like, support more advanced features such as streaming and long-running operations, and often provide much better performance. You may consider using a legacy client instead, if a modern client is not yet available for the service you want to use, or if you are not able to use gRPC on your infrastructure.
**For most users, we recommend the modern client, if one is available.** Compared with simple clients, modern clients are generally much easier to use and more Ruby-like, support more advanced features such as streaming and long-running operations, and often provide much better performance. You may consider using a simple client instead, if a modern client is not yet available for the service you want to use, or if you are not able to use gRPC on your infrastructure.
The [product documentation](https://developers.google.com/android/work/play/emm-api) may provide guidance regarding the preferred client library to use.

6
generated/google-apis-androidenterprise_v1/google-apis-androidenterprise_v1.gemspec
View File

@ -5,10 +5,10 @@ Gem::Specification.new do |gem|
gem.version = Google::Apis::AndroidenterpriseV1::GEM_VERSION
gem.authors = ["Google LLC"]
gem.email = "googleapis-packages@google.com"
gem.summary = "Legacy REST client for Google Play EMM API V1"
gem.summary = "Simple REST client for Google Play EMM API V1"
gem.description =
"This is the legacy REST client for Google Play EMM API V1." \
" Legacy REST clients are simple Ruby libraries that provide access to" \
"This is the simple REST client for Google Play EMM API V1." \
" Simple REST clients are Ruby client libraries that provide access to" \
" Google services via their HTTP REST API endpoints. These libraries are" \
" generated and updated automatically based on the discovery documents" \
" published by the service, and they handle most concerns such as" \

2
generated/google-apis-androidenterprise_v1/lib/google/apis/androidenterprise_v1/gem_version.rb
View File

@ -19,7 +19,7 @@ module Google
GEM_VERSION = "0.1.0"
# Version of the code generator used to generate this client
GENERATOR_VERSION = "0.1.0"
GENERATOR_VERSION = "0.1.1"
# Revision of the discovery document this client was generated from
REVISION = "20201125"

4
generated/google-apis-androidmanagement_v1/CHANGELOG.md
View File

@ -1,7 +1,7 @@
# Release history for google-apis-androidmanagement_v1
### v0.1.0 (2021-01-01)
### v0.1.0 (2021-01-07)
* Regenerated using generator version 0.1.1
* Regenerated from discovery document revision 20201209
* Regenerated using generator version 0.1.0

16
generated/google-apis-androidmanagement_v1/OVERVIEW.md
View File

@ -1,4 +1,4 @@
# Legacy REST client for version V1 of the Android Management API
# Simple REST client for version V1 of the Android Management API
This is a simple client library for version V1 of the Android Management API. It provides:
@ -7,7 +7,7 @@ This is a simple client library for version V1 of the Android Management API. It
* Integration with the googleauth gem for authentication using OAuth, API keys, and service accounts.
* Control of retry, pagination, and timeouts.
Note that although this client library is supported and will continue to be updated to track changes to the service, it is considered legacy. A more modern client may be available for many Google services, especially Cloud Platform services. See the section below titled *Which client should I use?* for more information.
Note that although this client library is supported and will continue to be updated to track changes to the service, it is otherwise considered complete and not under active development. Many Google services, especially Google Cloud Platform services, may provide a more modern client that is under more active development and improvement. See the section below titled *Which client should I use?* for more information.
## Getting started
@ -58,26 +58,26 @@ See the class reference docs for information on the methods you can call from a
## Documentation
More detailed descriptions of the Google legacy REST clients are available in two documents.
More detailed descriptions of the Google simple REST clients are available in two documents.
* The [Usage Guide](https://github.com/googleapis/google-api-ruby-client/blob/master/docs/usage-guide.md) discusses how to make API calls, how to use the provided data structures, and how to work the various features of the client library, including media upload and download, error handling, retries, pagination, and logging.
* The [Auth Guide](https://github.com/googleapis/google-api-ruby-client/blob/master/docs/auth-guide.md) discusses authentication in the client libraries, including API keys, OAuth 2.0, service accounts, and environment variables.
(Note: the above documents are written for the legacy clients in general, and their examples may not reflect the Androidmanagement service in particular.)
(Note: the above documents are written for the simple REST clients in general, and their examples may not reflect the Androidmanagement service in particular.)
For reference information on specific calls in the Android Management API, see the {Google::Apis::AndroidmanagementV1::AndroidManagementService class reference docs}.
## Which client should I use?
Google provides two types of Ruby API client libraries: **legacy REST clients** and **modern clients**.
Google provides two types of Ruby API client libraries: **simple REST clients** and **modern clients**.
This library, `google-apis-androidmanagement_v1`, is a legacy REST client. You can identify legacy clients by their gem names, which are always in the form `google-apis-<servicename>_<serviceversion>`. The legacy REST clients connect to HTTP/JSON REST endpoints and are automatically generated from service discovery documents. They support most API functionality, but their class interfaces are sometimes awkward.
This library, `google-apis-androidmanagement_v1`, is a simple REST client. You can identify these clients by their gem names, which are always in the form `google-apis-<servicename>_<serviceversion>`. The simple REST clients connect to HTTP/JSON REST endpoints and are automatically generated from service discovery documents. They support most API functionality, but their class interfaces are sometimes awkward.
Modern clients are produced by a modern code generator, combined with hand-crafted functionality for some services. Most modern clients connect to high-performance gRPC endpoints, although a few are backed by REST services. Modern clients are available for many Google services, especially Cloud Platform services, but do not yet support all the services covered by the legacy clients.
Modern clients are produced by a modern code generator, sometimes combined with hand-crafted functionality. Most modern clients connect to high-performance gRPC endpoints, although a few are backed by REST services. Modern clients are available for many Google services, especially Google Cloud Platform services, but do not yet support all the services covered by the simple clients.
Gem names for modern clients are often of the form `google-cloud-<service_name>`. (For example, [google-cloud-pubsub](https://rubygems.org/gems/google-cloud-pubsub).) Note that most modern clients also have corresponding "versioned" gems with names like `google-cloud-<service_name>-<version>`. (For example, [google-cloud-pubsub-v1](https://rubygems.org/gems/google-cloud-pubsub-v1).) The "versioned" gems can be used directly, but often provide lower-level interfaces. In most cases, the main gem is recommended.
**For most users, we recommend the modern client, if one is available.** Compared with legacy clients, modern clients are generally much easier to use and more Ruby-like, support more advanced features such as streaming and long-running operations, and often provide much better performance. You may consider using a legacy client instead, if a modern client is not yet available for the service you want to use, or if you are not able to use gRPC on your infrastructure.
**For most users, we recommend the modern client, if one is available.** Compared with simple clients, modern clients are generally much easier to use and more Ruby-like, support more advanced features such as streaming and long-running operations, and often provide much better performance. You may consider using a simple client instead, if a modern client is not yet available for the service you want to use, or if you are not able to use gRPC on your infrastructure.
The [product documentation](https://developers.google.com/android/management) may provide guidance regarding the preferred client library to use.

6
generated/google-apis-androidmanagement_v1/google-apis-androidmanagement_v1.gemspec
View File

@ -5,10 +5,10 @@ Gem::Specification.new do |gem|
gem.version = Google::Apis::AndroidmanagementV1::GEM_VERSION
gem.authors = ["Google LLC"]
gem.email = "googleapis-packages@google.com"
gem.summary = "Legacy REST client for Android Management API V1"
gem.summary = "Simple REST client for Android Management API V1"
gem.description =
"This is the legacy REST client for Android Management API V1." \
" Legacy REST clients are simple Ruby libraries that provide access to" \
"This is the simple REST client for Android Management API V1." \
" Simple REST clients are Ruby client libraries that provide access to" \
" Google services via their HTTP REST API endpoints. These libraries are" \
" generated and updated automatically based on the discovery documents" \
" published by the service, and they handle most concerns such as" \

2
generated/google-apis-androidmanagement_v1/lib/google/apis/androidmanagement_v1/gem_version.rb
View File

@ -19,7 +19,7 @@ module Google
GEM_VERSION = "0.1.0"
# Version of the code generator used to generate this client
GENERATOR_VERSION = "0.1.0"
GENERATOR_VERSION = "0.1.1"
# Revision of the discovery document this client was generated from
REVISION = "20201209"

4
generated/google-apis-androidpublisher_v3/CHANGELOG.md
View File

@ -1,7 +1,7 @@
# Release history for google-apis-androidpublisher_v3
### v0.1.0 (2021-01-01)
### v0.1.0 (2021-01-07)
* Regenerated using generator version 0.1.1
* Regenerated from discovery document revision 20201125
* Regenerated using generator version 0.1.0

16
generated/google-apis-androidpublisher_v3/OVERVIEW.md
View File

@ -1,4 +1,4 @@
# Legacy REST client for version V3 of the Google Play Android Developer API
# Simple REST client for version V3 of the Google Play Android Developer API
This is a simple client library for version V3 of the Google Play Android Developer API. It provides:
@ -7,7 +7,7 @@ This is a simple client library for version V3 of the Google Play Android Develo
* Integration with the googleauth gem for authentication using OAuth, API keys, and service accounts.
* Control of retry, pagination, and timeouts.
Note that although this client library is supported and will continue to be updated to track changes to the service, it is considered legacy. A more modern client may be available for many Google services, especially Cloud Platform services. See the section below titled *Which client should I use?* for more information.
Note that although this client library is supported and will continue to be updated to track changes to the service, it is otherwise considered complete and not under active development. Many Google services, especially Google Cloud Platform services, may provide a more modern client that is under more active development and improvement. See the section below titled *Which client should I use?* for more information.
## Getting started
@ -58,26 +58,26 @@ See the class reference docs for information on the methods you can call from a
## Documentation
More detailed descriptions of the Google legacy REST clients are available in two documents.
More detailed descriptions of the Google simple REST clients are available in two documents.
* The [Usage Guide](https://github.com/googleapis/google-api-ruby-client/blob/master/docs/usage-guide.md) discusses how to make API calls, how to use the provided data structures, and how to work the various features of the client library, including media upload and download, error handling, retries, pagination, and logging.
* The [Auth Guide](https://github.com/googleapis/google-api-ruby-client/blob/master/docs/auth-guide.md) discusses authentication in the client libraries, including API keys, OAuth 2.0, service accounts, and environment variables.
(Note: the above documents are written for the legacy clients in general, and their examples may not reflect the Androidpublisher service in particular.)
(Note: the above documents are written for the simple REST clients in general, and their examples may not reflect the Androidpublisher service in particular.)
For reference information on specific calls in the Google Play Android Developer API, see the {Google::Apis::AndroidpublisherV3::AndroidPublisherService class reference docs}.
## Which client should I use?
Google provides two types of Ruby API client libraries: **legacy REST clients** and **modern clients**.
Google provides two types of Ruby API client libraries: **simple REST clients** and **modern clients**.
This library, `google-apis-androidpublisher_v3`, is a legacy REST client. You can identify legacy clients by their gem names, which are always in the form `google-apis-<servicename>_<serviceversion>`. The legacy REST clients connect to HTTP/JSON REST endpoints and are automatically generated from service discovery documents. They support most API functionality, but their class interfaces are sometimes awkward.
This library, `google-apis-androidpublisher_v3`, is a simple REST client. You can identify these clients by their gem names, which are always in the form `google-apis-<servicename>_<serviceversion>`. The simple REST clients connect to HTTP/JSON REST endpoints and are automatically generated from service discovery documents. They support most API functionality, but their class interfaces are sometimes awkward.
Modern clients are produced by a modern code generator, combined with hand-crafted functionality for some services. Most modern clients connect to high-performance gRPC endpoints, although a few are backed by REST services. Modern clients are available for many Google services, especially Cloud Platform services, but do not yet support all the services covered by the legacy clients.
Modern clients are produced by a modern code generator, sometimes combined with hand-crafted functionality. Most modern clients connect to high-performance gRPC endpoints, although a few are backed by REST services. Modern clients are available for many Google services, especially Google Cloud Platform services, but do not yet support all the services covered by the simple clients.
Gem names for modern clients are often of the form `google-cloud-<service_name>`. (For example, [google-cloud-pubsub](https://rubygems.org/gems/google-cloud-pubsub).) Note that most modern clients also have corresponding "versioned" gems with names like `google-cloud-<service_name>-<version>`. (For example, [google-cloud-pubsub-v1](https://rubygems.org/gems/google-cloud-pubsub-v1).) The "versioned" gems can be used directly, but often provide lower-level interfaces. In most cases, the main gem is recommended.
**For most users, we recommend the modern client, if one is available.** Compared with legacy clients, modern clients are generally much easier to use and more Ruby-like, support more advanced features such as streaming and long-running operations, and often provide much better performance. You may consider using a legacy client instead, if a modern client is not yet available for the service you want to use, or if you are not able to use gRPC on your infrastructure.
**For most users, we recommend the modern client, if one is available.** Compared with simple clients, modern clients are generally much easier to use and more Ruby-like, support more advanced features such as streaming and long-running operations, and often provide much better performance. You may consider using a simple client instead, if a modern client is not yet available for the service you want to use, or if you are not able to use gRPC on your infrastructure.
The [product documentation](https://developers.google.com/android-publisher) may provide guidance regarding the preferred client library to use.

6
generated/google-apis-androidpublisher_v3/google-apis-androidpublisher_v3.gemspec
View File

@ -5,10 +5,10 @@ Gem::Specification.new do |gem|
gem.version = Google::Apis::AndroidpublisherV3::GEM_VERSION
gem.authors = ["Google LLC"]
gem.email = "googleapis-packages@google.com"
gem.summary = "Legacy REST client for Google Play Android Developer API V3"
gem.summary = "Simple REST client for Google Play Android Developer API V3"
gem.description =
"This is the legacy REST client for Google Play Android Developer API V3." \
" Legacy REST clients are simple Ruby libraries that provide access to" \
"This is the simple REST client for Google Play Android Developer API V3." \
" Simple REST clients are Ruby client libraries that provide access to" \
" Google services via their HTTP REST API endpoints. These libraries are" \
" generated and updated automatically based on the discovery documents" \
" published by the service, and they handle most concerns such as" \

2
generated/google-apis-androidpublisher_v3/lib/google/apis/androidpublisher_v3/gem_version.rb
View File

@ -19,7 +19,7 @@ module Google
GEM_VERSION = "0.1.0"
# Version of the code generator used to generate this client
GENERATOR_VERSION = "0.1.0"
GENERATOR_VERSION = "0.1.1"
# Revision of the discovery document this client was generated from
REVISION = "20201125"

4
generated/google-apis-apigateway_v1/CHANGELOG.md
View File

@ -1,7 +1,7 @@
# Release history for google-apis-apigateway_v1
### v0.1.0 (2021-01-01)
### v0.1.0 (2021-01-07)
* Regenerated using generator version 0.1.1
* Regenerated from discovery document revision 20201211
* Regenerated using generator version 0.1.0

16
generated/google-apis-apigateway_v1/OVERVIEW.md
View File

@ -1,4 +1,4 @@
# Legacy REST client for version V1 of the API Gateway API
# Simple REST client for version V1 of the API Gateway API
This is a simple client library for version V1 of the API Gateway API. It provides:
@ -7,7 +7,7 @@ This is a simple client library for version V1 of the API Gateway API. It provid
* Integration with the googleauth gem for authentication using OAuth, API keys, and service accounts.
* Control of retry, pagination, and timeouts.
Note that although this client library is supported and will continue to be updated to track changes to the service, it is considered legacy. A more modern client may be available for many Google services, especially Cloud Platform services. See the section below titled *Which client should I use?* for more information.
Note that although this client library is supported and will continue to be updated to track changes to the service, it is otherwise considered complete and not under active development. Many Google services, especially Google Cloud Platform services, may provide a more modern client that is under more active development and improvement. See the section below titled *Which client should I use?* for more information.
## Getting started
@ -58,26 +58,26 @@ See the class reference docs for information on the methods you can call from a
## Documentation
More detailed descriptions of the Google legacy REST clients are available in two documents.
More detailed descriptions of the Google simple REST clients are available in two documents.
* The [Usage Guide](https://github.com/googleapis/google-api-ruby-client/blob/master/docs/usage-guide.md) discusses how to make API calls, how to use the provided data structures, and how to work the various features of the client library, including media upload and download, error handling, retries, pagination, and logging.
* The [Auth Guide](https://github.com/googleapis/google-api-ruby-client/blob/master/docs/auth-guide.md) discusses authentication in the client libraries, including API keys, OAuth 2.0, service accounts, and environment variables.
(Note: the above documents are written for the legacy clients in general, and their examples may not reflect the Apigateway service in particular.)
(Note: the above documents are written for the simple REST clients in general, and their examples may not reflect the Apigateway service in particular.)
For reference information on specific calls in the API Gateway API, see the {Google::Apis::ApigatewayV1::ApigatewayService class reference docs}.
## Which client should I use?
Google provides two types of Ruby API client libraries: **legacy REST clients** and **modern clients**.
Google provides two types of Ruby API client libraries: **simple REST clients** and **modern clients**.
This library, `google-apis-apigateway_v1`, is a legacy REST client. You can identify legacy clients by their gem names, which are always in the form `google-apis-<servicename>_<serviceversion>`. The legacy REST clients connect to HTTP/JSON REST endpoints and are automatically generated from service discovery documents. They support most API functionality, but their class interfaces are sometimes awkward.
This library, `google-apis-apigateway_v1`, is a simple REST client. You can identify these clients by their gem names, which are always in the form `google-apis-<servicename>_<serviceversion>`. The simple REST clients connect to HTTP/JSON REST endpoints and are automatically generated from service discovery documents. They support most API functionality, but their class interfaces are sometimes awkward.
Modern clients are produced by a modern code generator, combined with hand-crafted functionality for some services. Most modern clients connect to high-performance gRPC endpoints, although a few are backed by REST services. Modern clients are available for many Google services, especially Cloud Platform services, but do not yet support all the services covered by the legacy clients.
Modern clients are produced by a modern code generator, sometimes combined with hand-crafted functionality. Most modern clients connect to high-performance gRPC endpoints, although a few are backed by REST services. Modern clients are available for many Google services, especially Google Cloud Platform services, but do not yet support all the services covered by the simple clients.
Gem names for modern clients are often of the form `google-cloud-<service_name>`. (For example, [google-cloud-pubsub](https://rubygems.org/gems/google-cloud-pubsub).) Note that most modern clients also have corresponding "versioned" gems with names like `google-cloud-<service_name>-<version>`. (For example, [google-cloud-pubsub-v1](https://rubygems.org/gems/google-cloud-pubsub-v1).) The "versioned" gems can be used directly, but often provide lower-level interfaces. In most cases, the main gem is recommended.
**For most users, we recommend the modern client, if one is available.** Compared with legacy clients, modern clients are generally much easier to use and more Ruby-like, support more advanced features such as streaming and long-running operations, and often provide much better performance. You may consider using a legacy client instead, if a modern client is not yet available for the service you want to use, or if you are not able to use gRPC on your infrastructure.
**For most users, we recommend the modern client, if one is available.** Compared with simple clients, modern clients are generally much easier to use and more Ruby-like, support more advanced features such as streaming and long-running operations, and often provide much better performance. You may consider using a simple client instead, if a modern client is not yet available for the service you want to use, or if you are not able to use gRPC on your infrastructure.
The [product documentation]( https://cloud.google.com/api-gateway/docs) may provide guidance regarding the preferred client library to use.

6
generated/google-apis-apigateway_v1/google-apis-apigateway_v1.gemspec
View File

@ -5,10 +5,10 @@ Gem::Specification.new do |gem|
gem.version = Google::Apis::ApigatewayV1::GEM_VERSION
gem.authors = ["Google LLC"]
gem.email = "googleapis-packages@google.com"
gem.summary = "Legacy REST client for API Gateway API V1"
gem.summary = "Simple REST client for API Gateway API V1"
gem.description =
"This is the legacy REST client for API Gateway API V1." \
" Legacy REST clients are simple Ruby libraries that provide access to" \
"This is the simple REST client for API Gateway API V1." \
" Simple REST clients are Ruby client libraries that provide access to" \
" Google services via their HTTP REST API endpoints. These libraries are" \
" generated and updated automatically based on the discovery documents" \
" published by the service, and they handle most concerns such as" \

2
generated/google-apis-apigateway_v1/lib/google/apis/apigateway_v1/gem_version.rb
View File

@ -19,7 +19,7 @@ module Google
GEM_VERSION = "0.1.0"
# Version of the code generator used to generate this client
GENERATOR_VERSION = "0.1.0"
GENERATOR_VERSION = "0.1.1"
# Revision of the discovery document this client was generated from
REVISION = "20201211"

Some files were not shown because too many files have changed in this diff Show More