Struct google_runtimeconfig1_beta1::ProjectConfigWaiterCreateCall [−][src]
pub struct ProjectConfigWaiterCreateCall<'a, C, A> where
C: 'a,
A: 'a, { /* fields omitted */ }
Creates a Waiter resource. This operation returns a long-running Operation resource which can be polled for completion. However, a waiter with the given name will exist (and can be retrieved) prior to the operation completing. If the operation fails, the failed Waiter resource will still exist and must be deleted prior to subsequent creation attempts.
A builder for the configs.waiters.create method supported by a project resource.
It is not used directly, but through a ProjectMethods
instance.
Example
Instantiate a resource method builder
use runtimeconfig1_beta1::Waiter; // As the method needs a request, you would usually fill it with the desired information // into the respective structure. Some of the parts shown here might not be applicable ! // Values shown here are possibly random and not representative ! let mut req = Waiter::default(); // You can configure optional parameters by calling the respective setters at will, and // execute the final call using `doit()`. // Values shown here are possibly random and not representative ! let result = hub.projects().configs_waiters_create(req, "parent") .request_id("no") .doit();
Methods
impl<'a, C, A> ProjectConfigWaiterCreateCall<'a, C, A> where
C: BorrowMut<Client>,
A: GetToken,
[src]
impl<'a, C, A> ProjectConfigWaiterCreateCall<'a, C, A> where
C: BorrowMut<Client>,
A: GetToken,
pub fn doit(self) -> Result<(Response, Operation)>
[src]
pub fn doit(self) -> Result<(Response, Operation)>
Perform the operation you have build so far.
pub fn request(
self,
new_value: Waiter
) -> ProjectConfigWaiterCreateCall<'a, C, A>
[src]
pub fn request(
self,
new_value: Waiter
) -> ProjectConfigWaiterCreateCall<'a, C, A>
Sets the request property to the given value.
Even though the property as already been set when instantiating this call, we provide this method for API completeness.
pub fn parent(self, new_value: &str) -> ProjectConfigWaiterCreateCall<'a, C, A>
[src]
pub fn parent(self, new_value: &str) -> ProjectConfigWaiterCreateCall<'a, C, A>
The path to the configuration that will own the waiter. The configuration must exist beforehand; the path must be in the format:
projects/[PROJECT_ID]/configs/[CONFIG_NAME]
.
Sets the parent path property to the given value.
Even though the property as already been set when instantiating this call, we provide this method for API completeness.
pub fn request_id(
self,
new_value: &str
) -> ProjectConfigWaiterCreateCall<'a, C, A>
[src]
pub fn request_id(
self,
new_value: &str
) -> ProjectConfigWaiterCreateCall<'a, C, A>
An optional but recommended unique request_id
. If the server
receives two create()
requests with the same
request_id
, then the second request will be ignored and the
first resource created and stored in the backend is returned.
Empty request_id
fields are ignored.
It is responsibility of the client to ensure uniqueness of the
request_id
strings.
request_id
strings are limited to 64 characters.
Sets the request id query property to the given value.
pub fn delegate(
self,
new_value: &'a mut Delegate
) -> ProjectConfigWaiterCreateCall<'a, C, A>
[src]
pub fn delegate(
self,
new_value: &'a mut Delegate
) -> ProjectConfigWaiterCreateCall<'a, C, A>
The delegate implementation is consulted whenever there is an intermediate result, or if something goes wrong while executing the actual API request.
It should be used to handle progress information, and to implement a certain level of resilience.
Sets the delegate property to the given value.
pub fn param<T>(
self,
name: T,
value: T
) -> ProjectConfigWaiterCreateCall<'a, C, A> where
T: AsRef<str>,
[src]
pub fn param<T>(
self,
name: T,
value: T
) -> ProjectConfigWaiterCreateCall<'a, C, A> where
T: AsRef<str>,
Set any additional parameter of the query string used in the request. It should be used to set parameters which are not yet available through their own setters.
Please note that this method must not be used to set any of the known paramters which have their own setter method. If done anyway, the request will fail.
Additional Parameters
- upload_protocol (query-string) - Upload protocol for media (e.g. "raw", "multipart").
- pp (query-boolean) - Pretty-print response.
- prettyPrint (query-boolean) - Returns response with indentations and line breaks.
- bearer_token (query-string) - OAuth bearer token.
- access_token (query-string) - OAuth access token.
- uploadType (query-string) - Legacy upload protocol for media (e.g. "media", "multipart").
- quotaUser (query-string) - Available to use for quota purposes for server-side applications. Can be any arbitrary string assigned to a user, but should not exceed 40 characters.
- callback (query-string) - JSONP
- oauth_token (query-string) - OAuth 2.0 token for the current user.
- key (query-string) - API key. Your API key identifies your project and provides you with API access, quota, and reports. Required unless you provide an OAuth 2.0 token.
- fields (query-string) - Selector specifying which fields to include in a partial response.
- alt (query-string) - Data format for response.
- $.xgafv (query-string) - V1 error format.
pub fn add_scope<T, S>(
self,
scope: T
) -> ProjectConfigWaiterCreateCall<'a, C, A> where
T: Into<Option<S>>,
S: AsRef<str>,
[src]
pub fn add_scope<T, S>(
self,
scope: T
) -> ProjectConfigWaiterCreateCall<'a, C, A> where
T: Into<Option<S>>,
S: AsRef<str>,
Identifies the authorization scope for the method you are building.
Use this method to actively specify which scope should be used, instead the default Scope
variant
Scope::CloudPlatform
.
The scope
will be added to a set of scopes. This is important as one can maintain access
tokens for more than one scope.
If None
is specified, then all scopes will be removed and no default scope will be used either.
In that case, you have to specify your API-key using the key
parameter (see the param()
function for details).
Usually there is more than one suitable scope to authorize an operation, some of which may encompass more rights than others. For example, for listing resources, a read-only scope will be sufficient, a read-write scope will do as well.
Trait Implementations
impl<'a, C, A> CallBuilder for ProjectConfigWaiterCreateCall<'a, C, A>
[src]
impl<'a, C, A> CallBuilder for ProjectConfigWaiterCreateCall<'a, C, A>
Auto Trait Implementations
impl<'a, C, A> !Send for ProjectConfigWaiterCreateCall<'a, C, A>
impl<'a, C, A> !Send for ProjectConfigWaiterCreateCall<'a, C, A>
impl<'a, C, A> !Sync for ProjectConfigWaiterCreateCall<'a, C, A>
impl<'a, C, A> !Sync for ProjectConfigWaiterCreateCall<'a, C, A>