update version to 1.0.10; republish 4 select crates

This commit is contained in:
Sebastian Thiel
2019-07-05 19:09:55 +08:00
parent 82e90709fc
commit 8c1ca2aa9b
1388 changed files with 7464 additions and 7464 deletions

View File

@@ -4,12 +4,12 @@
[package]
name = "google-cloudscheduler1"
version = "1.0.9+20190617"
version = "1.0.10+20190617"
authors = ["Sebastian Thiel <byronimo@gmail.com>"]
description = "A complete library to interact with Cloud Scheduler (protocol v1)"
repository = "https://github.com/Byron/google-apis-rs/tree/master/gen/cloudscheduler1"
homepage = "https://cloud.google.com/scheduler/"
documentation = "https://docs.rs/google-cloudscheduler1/1.0.9+20190617"
documentation = "https://docs.rs/google-cloudscheduler1/1.0.10+20190617"
license = "MIT"
keywords = ["cloudscheduler", "google", "protocol", "web", "api"]
autobins = false

View File

@@ -5,16 +5,16 @@ DO NOT EDIT !
-->
The `google-cloudscheduler1` library allows access to all features of the *Google Cloud Scheduler* service.
This documentation was generated from *Cloud Scheduler* crate version *1.0.9+20190617*, where *20190617* is the exact revision of the *cloudscheduler:v1* schema built by the [mako](http://www.makotemplates.org/) code generator *v1.0.9*.
This documentation was generated from *Cloud Scheduler* crate version *1.0.10+20190617*, where *20190617* is the exact revision of the *cloudscheduler:v1* schema built by the [mako](http://www.makotemplates.org/) code generator *v1.0.10*.
Everything else about the *Cloud Scheduler* *v1* API can be found at the
[official documentation site](https://cloud.google.com/scheduler/).
# Features
Handle the following *Resources* with ease from the central [hub](https://docs.rs/google-cloudscheduler1/1.0.9+20190617/google_cloudscheduler1/struct.CloudScheduler.html) ...
Handle the following *Resources* with ease from the central [hub](https://docs.rs/google-cloudscheduler1/1.0.10+20190617/google_cloudscheduler1/struct.CloudScheduler.html) ...
* projects
* [*locations get*](https://docs.rs/google-cloudscheduler1/1.0.9+20190617/google_cloudscheduler1/struct.ProjectLocationGetCall.html), [*locations jobs create*](https://docs.rs/google-cloudscheduler1/1.0.9+20190617/google_cloudscheduler1/struct.ProjectLocationJobCreateCall.html), [*locations jobs delete*](https://docs.rs/google-cloudscheduler1/1.0.9+20190617/google_cloudscheduler1/struct.ProjectLocationJobDeleteCall.html), [*locations jobs get*](https://docs.rs/google-cloudscheduler1/1.0.9+20190617/google_cloudscheduler1/struct.ProjectLocationJobGetCall.html), [*locations jobs list*](https://docs.rs/google-cloudscheduler1/1.0.9+20190617/google_cloudscheduler1/struct.ProjectLocationJobListCall.html), [*locations jobs patch*](https://docs.rs/google-cloudscheduler1/1.0.9+20190617/google_cloudscheduler1/struct.ProjectLocationJobPatchCall.html), [*locations jobs pause*](https://docs.rs/google-cloudscheduler1/1.0.9+20190617/google_cloudscheduler1/struct.ProjectLocationJobPauseCall.html), [*locations jobs resume*](https://docs.rs/google-cloudscheduler1/1.0.9+20190617/google_cloudscheduler1/struct.ProjectLocationJobResumeCall.html), [*locations jobs run*](https://docs.rs/google-cloudscheduler1/1.0.9+20190617/google_cloudscheduler1/struct.ProjectLocationJobRunCall.html) and [*locations list*](https://docs.rs/google-cloudscheduler1/1.0.9+20190617/google_cloudscheduler1/struct.ProjectLocationListCall.html)
* [*locations get*](https://docs.rs/google-cloudscheduler1/1.0.10+20190617/google_cloudscheduler1/struct.ProjectLocationGetCall.html), [*locations jobs create*](https://docs.rs/google-cloudscheduler1/1.0.10+20190617/google_cloudscheduler1/struct.ProjectLocationJobCreateCall.html), [*locations jobs delete*](https://docs.rs/google-cloudscheduler1/1.0.10+20190617/google_cloudscheduler1/struct.ProjectLocationJobDeleteCall.html), [*locations jobs get*](https://docs.rs/google-cloudscheduler1/1.0.10+20190617/google_cloudscheduler1/struct.ProjectLocationJobGetCall.html), [*locations jobs list*](https://docs.rs/google-cloudscheduler1/1.0.10+20190617/google_cloudscheduler1/struct.ProjectLocationJobListCall.html), [*locations jobs patch*](https://docs.rs/google-cloudscheduler1/1.0.10+20190617/google_cloudscheduler1/struct.ProjectLocationJobPatchCall.html), [*locations jobs pause*](https://docs.rs/google-cloudscheduler1/1.0.10+20190617/google_cloudscheduler1/struct.ProjectLocationJobPauseCall.html), [*locations jobs resume*](https://docs.rs/google-cloudscheduler1/1.0.10+20190617/google_cloudscheduler1/struct.ProjectLocationJobResumeCall.html), [*locations jobs run*](https://docs.rs/google-cloudscheduler1/1.0.10+20190617/google_cloudscheduler1/struct.ProjectLocationJobRunCall.html) and [*locations list*](https://docs.rs/google-cloudscheduler1/1.0.10+20190617/google_cloudscheduler1/struct.ProjectLocationListCall.html)
@@ -23,17 +23,17 @@ Handle the following *Resources* with ease from the central [hub](https://docs.r
The API is structured into the following primary items:
* **[Hub](https://docs.rs/google-cloudscheduler1/1.0.9+20190617/google_cloudscheduler1/struct.CloudScheduler.html)**
* **[Hub](https://docs.rs/google-cloudscheduler1/1.0.10+20190617/google_cloudscheduler1/struct.CloudScheduler.html)**
* a central object to maintain state and allow accessing all *Activities*
* creates [*Method Builders*](https://docs.rs/google-cloudscheduler1/1.0.9+20190617/google_cloudscheduler1/trait.MethodsBuilder.html) which in turn
allow access to individual [*Call Builders*](https://docs.rs/google-cloudscheduler1/1.0.9+20190617/google_cloudscheduler1/trait.CallBuilder.html)
* **[Resources](https://docs.rs/google-cloudscheduler1/1.0.9+20190617/google_cloudscheduler1/trait.Resource.html)**
* creates [*Method Builders*](https://docs.rs/google-cloudscheduler1/1.0.10+20190617/google_cloudscheduler1/trait.MethodsBuilder.html) which in turn
allow access to individual [*Call Builders*](https://docs.rs/google-cloudscheduler1/1.0.10+20190617/google_cloudscheduler1/trait.CallBuilder.html)
* **[Resources](https://docs.rs/google-cloudscheduler1/1.0.10+20190617/google_cloudscheduler1/trait.Resource.html)**
* primary types that you can apply *Activities* to
* a collection of properties and *Parts*
* **[Parts](https://docs.rs/google-cloudscheduler1/1.0.9+20190617/google_cloudscheduler1/trait.Part.html)**
* **[Parts](https://docs.rs/google-cloudscheduler1/1.0.10+20190617/google_cloudscheduler1/trait.Part.html)**
* a collection of properties
* never directly used in *Activities*
* **[Activities](https://docs.rs/google-cloudscheduler1/1.0.9+20190617/google_cloudscheduler1/trait.CallBuilder.html)**
* **[Activities](https://docs.rs/google-cloudscheduler1/1.0.10+20190617/google_cloudscheduler1/trait.CallBuilder.html)**
* operations to apply to *Resources*
All *structures* are marked with applicable traits to further categorize them and ease browsing.
@@ -136,17 +136,17 @@ match result {
```
## Handling Errors
All errors produced by the system are provided either as [Result](https://docs.rs/google-cloudscheduler1/1.0.9+20190617/google_cloudscheduler1/enum.Result.html) enumeration as return value of
All errors produced by the system are provided either as [Result](https://docs.rs/google-cloudscheduler1/1.0.10+20190617/google_cloudscheduler1/enum.Result.html) enumeration as return value of
the doit() methods, or handed as possibly intermediate results to either the
[Hub Delegate](https://docs.rs/google-cloudscheduler1/1.0.9+20190617/google_cloudscheduler1/trait.Delegate.html), or the [Authenticator Delegate](https://docs.rs/yup-oauth2/*/yup_oauth2/trait.AuthenticatorDelegate.html).
[Hub Delegate](https://docs.rs/google-cloudscheduler1/1.0.10+20190617/google_cloudscheduler1/trait.Delegate.html), or the [Authenticator Delegate](https://docs.rs/yup-oauth2/*/yup_oauth2/trait.AuthenticatorDelegate.html).
When delegates handle errors or intermediate values, they may have a chance to instruct the system to retry. This
makes the system potentially resilient to all kinds of errors.
## Uploads and Downloads
If a method supports downloads, the response body, which is part of the [Result](https://docs.rs/google-cloudscheduler1/1.0.9+20190617/google_cloudscheduler1/enum.Result.html), should be
If a method supports downloads, the response body, which is part of the [Result](https://docs.rs/google-cloudscheduler1/1.0.10+20190617/google_cloudscheduler1/enum.Result.html), should be
read by you to obtain the media.
If such a method also supports a [Response Result](https://docs.rs/google-cloudscheduler1/1.0.9+20190617/google_cloudscheduler1/trait.ResponseResult.html), it will return that by default.
If such a method also supports a [Response Result](https://docs.rs/google-cloudscheduler1/1.0.10+20190617/google_cloudscheduler1/trait.ResponseResult.html), it will return that by default.
You can see it as meta-data for the actual media. To trigger a media download, you will have to set up the builder by making
this call: `.param("alt", "media")`.
@@ -156,29 +156,29 @@ Methods supporting uploads can do so using up to 2 different protocols:
## Customization and Callbacks
You may alter the way an `doit()` method is called by providing a [delegate](https://docs.rs/google-cloudscheduler1/1.0.9+20190617/google_cloudscheduler1/trait.Delegate.html) to the
[Method Builder](https://docs.rs/google-cloudscheduler1/1.0.9+20190617/google_cloudscheduler1/trait.CallBuilder.html) before making the final `doit()` call.
You may alter the way an `doit()` method is called by providing a [delegate](https://docs.rs/google-cloudscheduler1/1.0.10+20190617/google_cloudscheduler1/trait.Delegate.html) to the
[Method Builder](https://docs.rs/google-cloudscheduler1/1.0.10+20190617/google_cloudscheduler1/trait.CallBuilder.html) before making the final `doit()` call.
Respective methods will be called to provide progress information, as well as determine whether the system should
retry on failure.
The [delegate trait](https://docs.rs/google-cloudscheduler1/1.0.9+20190617/google_cloudscheduler1/trait.Delegate.html) is default-implemented, allowing you to customize it with minimal effort.
The [delegate trait](https://docs.rs/google-cloudscheduler1/1.0.10+20190617/google_cloudscheduler1/trait.Delegate.html) is default-implemented, allowing you to customize it with minimal effort.
## Optional Parts in Server-Requests
All structures provided by this library are made to be [enocodable](https://docs.rs/google-cloudscheduler1/1.0.9+20190617/google_cloudscheduler1/trait.RequestValue.html) and
[decodable](https://docs.rs/google-cloudscheduler1/1.0.9+20190617/google_cloudscheduler1/trait.ResponseResult.html) via *json*. Optionals are used to indicate that partial requests are responses
All structures provided by this library are made to be [enocodable](https://docs.rs/google-cloudscheduler1/1.0.10+20190617/google_cloudscheduler1/trait.RequestValue.html) and
[decodable](https://docs.rs/google-cloudscheduler1/1.0.10+20190617/google_cloudscheduler1/trait.ResponseResult.html) via *json*. Optionals are used to indicate that partial requests are responses
are valid.
Most optionals are are considered [Parts](https://docs.rs/google-cloudscheduler1/1.0.9+20190617/google_cloudscheduler1/trait.Part.html) which are identifiable by name, which will be sent to
Most optionals are are considered [Parts](https://docs.rs/google-cloudscheduler1/1.0.10+20190617/google_cloudscheduler1/trait.Part.html) which are identifiable by name, which will be sent to
the server to indicate either the set parts of the request or the desired parts in the response.
## Builder Arguments
Using [method builders](https://docs.rs/google-cloudscheduler1/1.0.9+20190617/google_cloudscheduler1/trait.CallBuilder.html), you are able to prepare an action call by repeatedly calling it's methods.
Using [method builders](https://docs.rs/google-cloudscheduler1/1.0.10+20190617/google_cloudscheduler1/trait.CallBuilder.html), you are able to prepare an action call by repeatedly calling it's methods.
These will always take a single argument, for which the following statements are true.
* [PODs][wiki-pod] are handed by copy
* strings are passed as `&str`
* [request values](https://docs.rs/google-cloudscheduler1/1.0.9+20190617/google_cloudscheduler1/trait.RequestValue.html) are moved
* [request values](https://docs.rs/google-cloudscheduler1/1.0.10+20190617/google_cloudscheduler1/trait.RequestValue.html) are moved
Arguments will always be copied or cloned into the builder, to make them independent of their original life times.

View File

@@ -2,7 +2,7 @@
// This file was generated automatically from 'src/mako/api/lib.rs.mako'
// DO NOT EDIT !
//! This documentation was generated from *Cloud Scheduler* crate version *1.0.9+20190617*, where *20190617* is the exact revision of the *cloudscheduler:v1* schema built by the [mako](http://www.makotemplates.org/) code generator *v1.0.9*.
//! This documentation was generated from *Cloud Scheduler* crate version *1.0.10+20190617*, where *20190617* is the exact revision of the *cloudscheduler:v1* schema built by the [mako](http://www.makotemplates.org/) code generator *v1.0.10*.
//!
//! Everything else about the *Cloud Scheduler* *v1* API can be found at the
//! [official documentation site](https://cloud.google.com/scheduler/).
@@ -336,7 +336,7 @@ impl<'a, C, A> CloudScheduler<C, A>
CloudScheduler {
client: RefCell::new(client),
auth: RefCell::new(authenticator),
_user_agent: "google-api-rust-client/1.0.9".to_string(),
_user_agent: "google-api-rust-client/1.0.10".to_string(),
_base_url: "https://cloudscheduler.googleapis.com/".to_string(),
_root_url: "https://cloudscheduler.googleapis.com/".to_string(),
}
@@ -347,7 +347,7 @@ impl<'a, C, A> CloudScheduler<C, A>
}
/// Set the user-agent header field to use in all requests to the server.
/// It defaults to `google-api-rust-client/1.0.9`.
/// It defaults to `google-api-rust-client/1.0.10`.
///
/// Returns the previously set user-agent.
pub fn user_agent(&mut self, agent_name: String) -> String {