OMGeeky/google-apis-rs
1
0
Fork 0
mirror of https://github.com/OMGeeky/google-apis-rs.git synced 2026-01-25 04:35:18 +01:00
Code Issues Packages Projects Releases Wiki Activity

chore(code-gen): update to latest version

Browse Source 
Which is to be published
This commit is contained in:
Sebastian Thiel
2016-09-11 10:13:33 +02:00
parent 13ed4eaecb
commit 45d86f31f2
626 changed files with 285857 additions and 24274 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
gen/deploymentmanager2/src/lib.rs
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 *Deployment Manager* crate version *0.1.14+20160406*, where *20160406* is the exact revision of the *deploymentmanager:v2* schema built by the [mako](http://www.makotemplates.org/) code generator *v0.1.14*.
//! This documentation was generated from *Deployment Manager* crate version *0.1.14+20160901*, where *20160901* is the exact revision of the *deploymentmanager:v2* schema built by the [mako](http://www.makotemplates.org/) code generator *v0.1.14*.
//!
//! Everything else about the *Deployment Manager* *v2* API can be found at the
//! [official documentation site](https://cloud.google.com/deployment-manager/).

26
gen/deploymentmanager2/src/lib.rs.in
View File

@@ -235,7 +235,7 @@ pub struct ResourceType {
/// [Output Only] Timestamp when the resource was created or acquired, in RFC3339 text format .
#[serde(rename="insertTime")]
pub insert_time: Option<String>,
/// [Output Only] The type of the resource, for example compute.v1.instance, or replicaPools.v1beta2.instanceGroupManager.
/// [Output Only] The type of the resource, for example compute.v1.instance, or cloudfunctions.v1beta1.function.
#[serde(rename="type")]
pub type_: Option<String>,
/// [Output Only] Unique identifier for the resource; defined by the server.
@@ -486,6 +486,8 @@ impl ResponseResult for OperationsListResponse {}
///
#[derive(Default, Clone, Debug, Serialize, Deserialize)]
pub struct Type {
/// [Output Only] The Operation that most recently ran, or is currently running, on this type.
pub operation: Option<Operation>,
/// [Output Only] Timestamp when the type was created, in RFC3339 text format.
#[serde(rename="insertTime")]
pub insert_time: Option<String>,
@@ -807,7 +809,7 @@ pub struct Operation {
/// [Output Only] An optional textual description of the current status of the operation.
#[serde(rename="statusMessage")]
pub status_message: Option<String>,
/// [Output Only] The URL of the resource that the operation modifies.
/// [Output Only] The URL of the resource that the operation modifies. If creating a persistent disk snapshot, this points to the persistent disk that the snapshot was created from.
#[serde(rename="targetLink")]
pub target_link: Option<String>,
}
@@ -1848,9 +1850,9 @@ impl<'a, C, A> OperationListCall<'a, C, A> where C: BorrowMut<hyper::Client>, A:
///
/// For example, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.
///
/// Compute Engine Beta API Only: When filtering in the Beta API, you can also filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.
/// You can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.
///
/// The Beta API also supports filtering on multiple expressions by providing each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.
/// To filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.
///
/// Sets the *filter* query property to the given value.
pub fn filter(mut self, new_value: &str) -> OperationListCall<'a, C, A> {
@@ -2139,9 +2141,9 @@ impl<'a, C, A> ManifestListCall<'a, C, A> where C: BorrowMut<hyper::Client>, A:
///
/// For example, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.
///
/// Compute Engine Beta API Only: When filtering in the Beta API, you can also filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.
/// You can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.
///
/// The Beta API also supports filtering on multiple expressions by providing each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.
/// To filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.
///
/// Sets the *filter* query property to the given value.
pub fn filter(mut self, new_value: &str) -> ManifestListCall<'a, C, A> {
@@ -2677,9 +2679,9 @@ impl<'a, C, A> TypeListCall<'a, C, A> where C: BorrowMut<hyper::Client>, A: oaut
///
/// For example, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.
///
/// Compute Engine Beta API Only: When filtering in the Beta API, you can also filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.
/// You can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.
///
/// The Beta API also supports filtering on multiple expressions by providing each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.
/// To filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.
///
/// Sets the *filter* query property to the given value.
pub fn filter(mut self, new_value: &str) -> TypeListCall<'a, C, A> {
@@ -3227,9 +3229,9 @@ impl<'a, C, A> ResourceListCall<'a, C, A> where C: BorrowMut<hyper::Client>, A:
///
/// For example, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.
///
/// Compute Engine Beta API Only: When filtering in the Beta API, you can also filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.
/// You can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.
///
/// The Beta API also supports filtering on multiple expressions by providing each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.
/// To filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.
///
/// Sets the *filter* query property to the given value.
pub fn filter(mut self, new_value: &str) -> ResourceListCall<'a, C, A> {
@@ -4623,9 +4625,9 @@ impl<'a, C, A> DeploymentListCall<'a, C, A> where C: BorrowMut<hyper::Client>, A
///
/// For example, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.
///
/// Compute Engine Beta API Only: When filtering in the Beta API, you can also filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.
/// You can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.
///
/// The Beta API also supports filtering on multiple expressions by providing each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.
/// To filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.
///
/// Sets the *filter* query property to the given value.
pub fn filter(mut self, new_value: &str) -> DeploymentListCall<'a, C, A> {