Struct google_healthcare1_beta1::api::ProjectLocationDatasetConsentStoreConsentListRevisionCall
source · pub struct ProjectLocationDatasetConsentStoreConsentListRevisionCall<'a, S>where
S: 'a,{ /* private fields */ }Expand description
Lists the revisions of the specified Consent in reverse chronological order.
A builder for the locations.datasets.consentStores.consents.listRevisions method supported by a project resource.
It is not used directly, but through a ProjectMethods instance.
§Example
Instantiate a resource method builder
// 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().locations_datasets_consent_stores_consents_list_revisions("name")
.page_token("diam")
.page_size(-61)
.filter("ipsum")
.doit().await;Implementations§
source§impl<'a, S> ProjectLocationDatasetConsentStoreConsentListRevisionCall<'a, S>
impl<'a, S> ProjectLocationDatasetConsentStoreConsentListRevisionCall<'a, S>
sourcepub async fn doit(
self
) -> Result<(Response<Body>, ListConsentRevisionsResponse)>
pub async fn doit( self ) -> Result<(Response<Body>, ListConsentRevisionsResponse)>
Perform the operation you have build so far.
sourcepub fn name(
self,
new_value: &str
) -> ProjectLocationDatasetConsentStoreConsentListRevisionCall<'a, S>
pub fn name( self, new_value: &str ) -> ProjectLocationDatasetConsentStoreConsentListRevisionCall<'a, S>
Required. The resource name of the Consent to retrieve revisions for.
Sets the name 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.
sourcepub fn page_token(
self,
new_value: &str
) -> ProjectLocationDatasetConsentStoreConsentListRevisionCall<'a, S>
pub fn page_token( self, new_value: &str ) -> ProjectLocationDatasetConsentStoreConsentListRevisionCall<'a, S>
Optional. Token to retrieve the next page of results or empty if there are no more results in the list.
Sets the page token query property to the given value.
sourcepub fn page_size(
self,
new_value: i32
) -> ProjectLocationDatasetConsentStoreConsentListRevisionCall<'a, S>
pub fn page_size( self, new_value: i32 ) -> ProjectLocationDatasetConsentStoreConsentListRevisionCall<'a, S>
Optional. Limit on the number of revisions to return in a single response. If not specified, 100 is used. May not be larger than 1000.
Sets the page size query property to the given value.
sourcepub fn filter(
self,
new_value: &str
) -> ProjectLocationDatasetConsentStoreConsentListRevisionCall<'a, S>
pub fn filter( self, new_value: &str ) -> ProjectLocationDatasetConsentStoreConsentListRevisionCall<'a, S>
Optional. Restricts the revisions returned to those matching a filter. The following syntax is available: * A string field value can be written as text inside quotation marks, for example "query text". The only valid relational operation for text fields is equality (=), where text is searched within the field, rather than having the field be equal to the text. For example, "Comment = great" returns messages with great in the comment field. * A number field value can be written as an integer, a decimal, or an exponential. The valid relational operators for number fields are the equality operator (=), along with the less than/greater than operators (<, <=, >, >=). Note that there is no inequality (!=) operator. You can prepend the NOT operator to an expression to negate it. * A date field value must be written in yyyy-mm-dd form. Fields with date and time use the RFC3339 time format. Leading zeros are required for one-digit months and days. The valid relational operators for date fields are the equality operator (=) , along with the less than/greater than operators (<, <=, >, >=). Note that there is no inequality (!=) operator. You can prepend the NOT operator to an expression to negate it. * Multiple field query expressions can be combined in one query by adding AND or OR operators between the expressions. If a boolean operator appears within a quoted string, it is not treated as special, it’s just another part of the character string to be matched. You can prepend the NOT operator to an expression to negate it. Fields/functions available for filtering are: - user_id. For example, filter='user_id="user123"'. - consent_artifact - state - revision_create_time - metadata. For example, filter=Metadata(\"testkey\")=\"value\" or filter=HasMetadata(\"testkey\").
Sets the filter query property to the given value.
sourcepub fn delegate(
self,
new_value: &'a mut dyn Delegate
) -> ProjectLocationDatasetConsentStoreConsentListRevisionCall<'a, S>
pub fn delegate( self, new_value: &'a mut dyn Delegate ) -> ProjectLocationDatasetConsentStoreConsentListRevisionCall<'a, S>
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.
sourcepub fn param<T>(
self,
name: T,
value: T
) -> ProjectLocationDatasetConsentStoreConsentListRevisionCall<'a, S>
pub fn param<T>( self, name: T, value: T ) -> ProjectLocationDatasetConsentStoreConsentListRevisionCall<'a, S>
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 parameters which have their own setter method. If done anyway, the request will fail.
§Additional Parameters
- $.xgafv (query-string) - V1 error format.
- access_token (query-string) - OAuth access token.
- alt (query-string) - Data format for response.
- callback (query-string) - JSONP
- fields (query-string) - Selector specifying which fields to include in a partial response.
- 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.
- oauth_token (query-string) - OAuth 2.0 token for the current user.
- prettyPrint (query-boolean) - Returns response with indentations and line breaks.
- 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.
- uploadType (query-string) - Legacy upload protocol for media (e.g. “media”, “multipart”).
- upload_protocol (query-string) - Upload protocol for media (e.g. “raw”, “multipart”).
sourcepub fn add_scope<St>(
self,
scope: St
) -> ProjectLocationDatasetConsentStoreConsentListRevisionCall<'a, S>
pub fn add_scope<St>( self, scope: St ) -> ProjectLocationDatasetConsentStoreConsentListRevisionCall<'a, S>
Identifies the authorization scope for the method you are building.
Use this method to actively specify which scope should be used, instead of the default Scope variant
Scope::CloudHealthcare.
The scope will be added to a set of scopes. This is important as one can maintain access
tokens for more than one scope.
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.
sourcepub fn add_scopes<I, St>(
self,
scopes: I
) -> ProjectLocationDatasetConsentStoreConsentListRevisionCall<'a, S>
pub fn add_scopes<I, St>( self, scopes: I ) -> ProjectLocationDatasetConsentStoreConsentListRevisionCall<'a, S>
Identifies the authorization scope(s) for the method you are building.
See Self::add_scope() for details.
sourcepub fn clear_scopes(
self
) -> ProjectLocationDatasetConsentStoreConsentListRevisionCall<'a, S>
pub fn clear_scopes( self ) -> ProjectLocationDatasetConsentStoreConsentListRevisionCall<'a, S>
Removes all scopes, and no default scope will be used either.
In this case, you have to specify your API-key using the key parameter (see Self::param()
for details).