Regenerate cloudscheduler client (googleapis#2059)

Author: yoshi-automation

clients/google-api-services-cloudscheduler/v1.metadata.json

@@ -2,6 +2,6 @@
   "maven": {
     "groupId": "com.google.apis",
     "artifactId": "google-api-services-cloudscheduler",
-    "version": "v1-rev20190429-1.28.0"
+    "version": "v1-rev20190604-1.28.0"
   }
 }

clients/google-api-services-cloudscheduler/v1/1.26.0/com/google/api/services/cloudscheduler/v1/model/HttpTarget.java

@@ -68,7 +68,8 @@ public final class HttpTarget extends com.google.api.client.json.GenericJson {
    * If specified, an [OAuth token](https://developers.google.com/identity/protocols/OAuth2) will be
    * generated and attached as an `Authorization` header in the HTTP request.
    *
-   * This type of authorization should be used when sending requests to a GCP endpoint.
+   * This type of authorization should generally only be used when calling Google APIs hosted on
+   * *.googleapis.com.
    * The value may be {@code null}.
    */
   @com.google.api.client.util.Key
@@ -78,8 +79,8 @@ public final class HttpTarget extends com.google.api.client.json.GenericJson {
    * If specified, an [OIDC](https://developers.google.com/identity/protocols/OpenIDConnect) token
    * will be generated and attached as an `Authorization` header in the HTTP request.
    *
-   * This type of authorization should be used when sending requests to third party endpoints or
-   * Cloud Run.
+   * This type of authorization can be used for many scenarios, including calling Cloud Run, or
+   * endpoints where you intend to validate the token yourself.
    * The value may be {@code null}.
    */
   @com.google.api.client.util.Key
@@ -202,7 +203,8 @@ public HttpTarget setHttpMethod(java.lang.String httpMethod) {
    * If specified, an [OAuth token](https://developers.google.com/identity/protocols/OAuth2) will be
    * generated and attached as an `Authorization` header in the HTTP request.
    *
-   * This type of authorization should be used when sending requests to a GCP endpoint.
+   * This type of authorization should generally only be used when calling Google APIs hosted on
+   * *.googleapis.com.
    * @return value or {@code null} for none
    */
   public OAuthToken getOauthToken() {
@@ -213,7 +215,8 @@ public OAuthToken getOauthToken() {
    * If specified, an [OAuth token](https://developers.google.com/identity/protocols/OAuth2) will be
    * generated and attached as an `Authorization` header in the HTTP request.
    *
-   * This type of authorization should be used when sending requests to a GCP endpoint.
+   * This type of authorization should generally only be used when calling Google APIs hosted on
+   * *.googleapis.com.
    * @param oauthToken oauthToken or {@code null} for none
    */
   public HttpTarget setOauthToken(OAuthToken oauthToken) {
@@ -225,8 +228,8 @@ public HttpTarget setOauthToken(OAuthToken oauthToken) {
    * If specified, an [OIDC](https://developers.google.com/identity/protocols/OpenIDConnect) token
    * will be generated and attached as an `Authorization` header in the HTTP request.
    *
-   * This type of authorization should be used when sending requests to third party endpoints or
-   * Cloud Run.
+   * This type of authorization can be used for many scenarios, including calling Cloud Run, or
+   * endpoints where you intend to validate the token yourself.
    * @return value or {@code null} for none
    */
   public OidcToken getOidcToken() {
@@ -237,8 +240,8 @@ public OidcToken getOidcToken() {
    * If specified, an [OIDC](https://developers.google.com/identity/protocols/OpenIDConnect) token
    * will be generated and attached as an `Authorization` header in the HTTP request.
    *
-   * This type of authorization should be used when sending requests to third party endpoints or
-   * Cloud Run.
+   * This type of authorization can be used for many scenarios, including calling Cloud Run, or
+   * endpoints where you intend to validate the token yourself.
    * @param oidcToken oidcToken or {@code null} for none
    */
   public HttpTarget setOidcToken(OidcToken oidcToken) {

clients/google-api-services-cloudscheduler/v1/1.26.0/com/google/api/services/cloudscheduler/v1/model/OAuthToken.java

@@ -19,7 +19,7 @@
 /**
  * Contains information needed for generating an [OAuth
  * token](https://developers.google.com/identity/protocols/OAuth2). This type of authorization
- * should be used when sending requests to a GCP endpoint.
+ * should generally only be used when calling Google APIs hosted on *.googleapis.com.
  *
  * <p> This is the Java data model class that specifies how to parse/serialize into the JSON that is
  * transmitted over HTTP when working with the Cloud Scheduler API. For a detailed explanation see:

clients/google-api-services-cloudscheduler/v1/1.26.0/com/google/api/services/cloudscheduler/v1/model/OidcToken.java

@@ -19,7 +19,8 @@
 /**
  * Contains information needed for generating an [OpenID Connect
  * token](https://developers.google.com/identity/protocols/OpenIDConnect). This type of
- * authorization should be used when sending requests to third party endpoints or Cloud Run.
+ * authorization can be used for many scenarios, including calling Cloud Run, or endpoints where you
+ * intend to validate the token yourself.
  *
  * <p> This is the Java data model class that specifies how to parse/serialize into the JSON that is
  * transmitted over HTTP when working with the Cloud Scheduler API. For a detailed explanation see:

clients/google-api-services-cloudscheduler/v1/1.26.0/com/google/api/services/cloudscheduler/v1/model/Status.java

@@ -19,49 +19,11 @@
 /**
  * The `Status` type defines a logical error model that is suitable for different programming
  * environments, including REST APIs and RPC APIs. It is used by [gRPC](https://github.com/grpc).
- * The error model is designed to be:
+ * Each `Status` message contains three pieces of data: error code, error message, and error
+ * details.
  *
- * - Simple to use and understand for most users - Flexible enough to meet unexpected needs
- *
- * # Overview
- *
- * The `Status` message contains three pieces of data: error code, error message, and error details.
- * The error code should be an enum value of google.rpc.Code, but it may accept additional error
- * codes if needed.  The error message should be a developer-facing English message that helps
- * developers *understand* and *resolve* the error. If a localized user-facing error message is
- * needed, put the localized message in the error details or localize it in the client. The optional
- * error details may contain arbitrary information about the error. There is a predefined set of
- * error detail types in the package `google.rpc` that can be used for common error conditions.
- *
- * # Language mapping
- *
- * The `Status` message is the logical representation of the error model, but it is not necessarily
- * the actual wire format. When the `Status` message is exposed in different client libraries and
- * different wire protocols, it can be mapped differently. For example, it will likely be mapped to
- * some exceptions in Java, but more likely mapped to some error codes in C.
- *
- * # Other uses
- *
- * The error model and the `Status` message can be used in a variety of environments, either with or
- * without APIs, to provide a consistent developer experience across different environments.
- *
- * Example uses of this error model include:
- *
- * - Partial errors. If a service needs to return partial errors to the client,     it may embed the
- * `Status` in the normal response to indicate the partial     errors.
- *
- * - Workflow errors. A typical workflow has multiple steps. Each step may     have a `Status`
- * message for error reporting.
- *
- * - Batch operations. If a client uses batch request and batch response, the     `Status` message
- * should be used directly inside batch response, one for     each error sub-response.
- *
- * - Asynchronous operations. If an API call embeds asynchronous operation     results in its
- * response, the status of those operations should be     represented directly using the `Status`
- * message.
- *
- * - Logging. If some API errors are stored in logs, the message `Status` could     be used directly
- * after any stripping needed for security/privacy reasons.
+ * You can find out more about this error model and how to work with it in the [API Design
+ * Guide](https://cloud.google.com/apis/design/errors).
  *
  * <p> This is the Java data model class that specifies how to parse/serialize into the JSON that is
  * transmitted over HTTP when working with the Cloud Scheduler API. For a detailed explanation see:

clients/google-api-services-cloudscheduler/v1/1.26.0/pom.xml

@@ -8,8 +8,8 @@
 
   <groupId>com.google.apis</groupId>
   <artifactId>google-api-services-cloudscheduler</artifactId>
-  <version>v1-rev20190429-1.26.0</version>
-  <name>Cloud Scheduler API v1-rev20190429-1.26.0</name>
+  <version>v1-rev20190604-1.26.0</version>
+  <name>Cloud Scheduler API v1-rev20190604-1.26.0</name>
   <packaging>jar</packaging>
 
   <inceptionYear>2011</inceptionYear>