Struct ProjectLocationMetadataStoreContextListCall 

pub struct ProjectLocationMetadataStoreContextListCall<'a, C>
where
    C: 'a,
{ /* private fields */ }

Lists Contexts on the MetadataStore.

A builder for the locations.metadataStores.contexts.list 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_metadata_stores_contexts_list("parent")
             .page_token("sadipscing")
             .page_size(-3)
             .order_by("ipsum")
             .filter("amet.")
             .doit().await;

Implementations

impl<'a, C> ProjectLocationMetadataStoreContextListCall<'a, C>

where C: Connector,

pub async fn doit( self, ) -> Result<(Response, GoogleCloudAiplatformV1ListContextsResponse)>

Perform the operation you have build so far.

pub fn parent( self, new_value: &str, ) -> ProjectLocationMetadataStoreContextListCall<'a, C>

Required. The MetadataStore whose Contexts should be listed. Format: projects/{project}/locations/{location}/metadataStores/{metadatastore}

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 page_token( self, new_value: &str, ) -> ProjectLocationMetadataStoreContextListCall<'a, C>

A page token, received from a previous MetadataService.ListContexts call. Provide this to retrieve the subsequent page. When paginating, all other provided parameters must match the call that provided the page token. (Otherwise the request will fail with INVALID_ARGUMENT error.)

Sets the page token query property to the given value.

pub fn page_size( self, new_value: i32, ) -> ProjectLocationMetadataStoreContextListCall<'a, C>

The maximum number of Contexts to return. The service may return fewer. Must be in range 1-1000, inclusive. Defaults to 100.

Sets the page size query property to the given value.

pub fn order_by( self, new_value: &str, ) -> ProjectLocationMetadataStoreContextListCall<'a, C>

How the list of messages is ordered. Specify the values to order by and an ordering operation. The default sorting order is ascending. To specify descending order for a field, users append a “ desc“ suffix; for example: “foo desc, bar”. Subfields are specified with a . character, such as foo.bar. see https://google.aip.dev/132#ordering for more details.

Sets the order by query property to the given value.

pub fn filter( self, new_value: &str, ) -> ProjectLocationMetadataStoreContextListCall<'a, C>

Filter specifying the boolean condition for the Contexts to satisfy in order to be part of the result set. The syntax to define filter query is based on https://google.aip.dev/160. Following are the supported set of filters: * Attribute filtering: For example: display_name = "test". Supported fields include: name, display_name, schema_title, create_time, and update_time. Time fields, such as create_time and update_time, require values specified in RFC-3339 format. For example: create_time = "2020-11-19T11:30:00-04:00". * Metadata field: To filter on metadata fields use traversal operation as follows: metadata... For example: metadata.field_1.number_value = 10.0. In case the field name contains special characters (such as colon), one can embed it inside double quote. For example: metadata."field:1".number_value = 10.0 * Parent Child filtering: To filter Contexts based on parent-child relationship use the HAS operator as follows: parent_contexts: "projects//locations//metadataStores//contexts/" child_contexts: "projects//locations//metadataStores//contexts/" Each of the above supported filters can be combined together using logical operators (AND & OR). Maximum nested expression depth allowed is 5. For example: display_name = "test" AND metadata.field1.bool_value = true.

Sets the filter query property to the given value.

pub fn delegate( self, new_value: &'a mut dyn Delegate, ) -> ProjectLocationMetadataStoreContextListCall<'a, C>

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, ) -> ProjectLocationMetadataStoreContextListCall<'a, C>

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 parameters which have their own setter method. If done anyway, the request will fail.

Additional Parameters

• $.xgafv (query-string) - V1 error format.
• 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.
• upload_protocol (query-string) - Upload protocol for media (e.g. “raw”, “multipart”).
• uploadType (query-string) - Legacy upload protocol for media (e.g. “media”, “multipart”).
• 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.
• oauth_token (query-string) - OAuth 2.0 token for the current user.
• access_token (query-string) - OAuth access token.
• callback (query-string) - JSONP
• alt (query-string) - Data format for response.

pub fn add_scope<St>( self, scope: St, ) -> ProjectLocationMetadataStoreContextListCall<'a, C>

where St: AsRef<str>,

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::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.

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.

pub fn add_scopes<I, St>( self, scopes: I, ) -> ProjectLocationMetadataStoreContextListCall<'a, C>

where I: IntoIterator<Item = St>, St: AsRef<str>,

Identifies the authorization scope(s) for the method you are building.

See Self::add_scope() for details.

pub fn clear_scopes(self) -> ProjectLocationMetadataStoreContextListCall<'a, C>

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).

Trait Implementations

impl<'a, C> CallBuilder for ProjectLocationMetadataStoreContextListCall<'a, C>