aws_sdk_datazone/client/

list_lineage_node_history.rs

// Code generated by software.amazon.smithy.rust.codegen.smithy-rs. DO NOT EDIT.
impl super::Client {
    /// Constructs a fluent builder for the [`ListLineageNodeHistory`](crate::operation::list_lineage_node_history::builders::ListLineageNodeHistoryFluentBuilder) operation.
    /// This operation supports pagination; See [`into_paginator()`](crate::operation::list_lineage_node_history::builders::ListLineageNodeHistoryFluentBuilder::into_paginator).
    ///
    /// - The fluent builder is configurable:
    ///   - [`domain_identifier(impl Into<String>)`](crate::operation::list_lineage_node_history::builders::ListLineageNodeHistoryFluentBuilder::domain_identifier) / [`set_domain_identifier(Option<String>)`](crate::operation::list_lineage_node_history::builders::ListLineageNodeHistoryFluentBuilder::set_domain_identifier):<br>required: **true**<br><p>The ID of the domain where you want to list the history of the specified data lineage node.</p><br>
    ///   - [`max_results(i32)`](crate::operation::list_lineage_node_history::builders::ListLineageNodeHistoryFluentBuilder::max_results) / [`set_max_results(Option<i32>)`](crate::operation::list_lineage_node_history::builders::ListLineageNodeHistoryFluentBuilder::set_max_results):<br>required: **false**<br><p>The maximum number of history items to return in a single call to ListLineageNodeHistory. When the number of memberships to be listed is greater than the value of MaxResults, the response contains a NextToken value that you can use in a subsequent call to ListLineageNodeHistory to list the next set of items.</p><br>
    ///   - [`next_token(impl Into<String>)`](crate::operation::list_lineage_node_history::builders::ListLineageNodeHistoryFluentBuilder::next_token) / [`set_next_token(Option<String>)`](crate::operation::list_lineage_node_history::builders::ListLineageNodeHistoryFluentBuilder::set_next_token):<br>required: **false**<br><p>When the number of history items is greater than the default value for the MaxResults parameter, or if you explicitly specify a value for MaxResults that is less than the number of items, the response includes a pagination token named NextToken. You can specify this NextToken value in a subsequent call to ListLineageNodeHistory to list the next set of items.</p><br>
    ///   - [`identifier(impl Into<String>)`](crate::operation::list_lineage_node_history::builders::ListLineageNodeHistoryFluentBuilder::identifier) / [`set_identifier(Option<String>)`](crate::operation::list_lineage_node_history::builders::ListLineageNodeHistoryFluentBuilder::set_identifier):<br>required: **true**<br><p>The ID of the data lineage node whose history you want to list.</p><br>
    ///   - [`direction(EdgeDirection)`](crate::operation::list_lineage_node_history::builders::ListLineageNodeHistoryFluentBuilder::direction) / [`set_direction(Option<EdgeDirection>)`](crate::operation::list_lineage_node_history::builders::ListLineageNodeHistoryFluentBuilder::set_direction):<br>required: **false**<br><p>The direction of the data lineage node refers to the lineage node having neighbors in that direction. For example, if direction is <code>UPSTREAM</code>, the <code>ListLineageNodeHistory</code> API responds with historical versions with upstream neighbors only.</p><br>
    ///   - [`event_timestamp_gte(DateTime)`](crate::operation::list_lineage_node_history::builders::ListLineageNodeHistoryFluentBuilder::event_timestamp_gte) / [`set_event_timestamp_gte(Option<DateTime>)`](crate::operation::list_lineage_node_history::builders::ListLineageNodeHistoryFluentBuilder::set_event_timestamp_gte):<br>required: **false**<br><p>Specifies whether the action is to return data lineage node history from the time after the event timestamp.</p><br>
    ///   - [`event_timestamp_lte(DateTime)`](crate::operation::list_lineage_node_history::builders::ListLineageNodeHistoryFluentBuilder::event_timestamp_lte) / [`set_event_timestamp_lte(Option<DateTime>)`](crate::operation::list_lineage_node_history::builders::ListLineageNodeHistoryFluentBuilder::set_event_timestamp_lte):<br>required: **false**<br><p>Specifies whether the action is to return data lineage node history from the time prior of the event timestamp.</p><br>
    ///   - [`sort_order(SortOrder)`](crate::operation::list_lineage_node_history::builders::ListLineageNodeHistoryFluentBuilder::sort_order) / [`set_sort_order(Option<SortOrder>)`](crate::operation::list_lineage_node_history::builders::ListLineageNodeHistoryFluentBuilder::set_sort_order):<br>required: **false**<br><p>The order by which you want data lineage node history to be sorted.</p><br>
    /// - On success, responds with [`ListLineageNodeHistoryOutput`](crate::operation::list_lineage_node_history::ListLineageNodeHistoryOutput) with field(s):
    ///   - [`nodes(Option<Vec::<LineageNodeSummary>>)`](crate::operation::list_lineage_node_history::ListLineageNodeHistoryOutput::nodes): <p>The nodes returned by the ListLineageNodeHistory action.</p>
    ///   - [`next_token(Option<String>)`](crate::operation::list_lineage_node_history::ListLineageNodeHistoryOutput::next_token): <p>When the number of history items is greater than the default value for the MaxResults parameter, or if you explicitly specify a value for MaxResults that is less than the number of items, the response includes a pagination token named NextToken. You can specify this NextToken value in a subsequent call to ListLineageNodeHistory to list the next set of items.</p>
    /// - On failure, responds with [`SdkError<ListLineageNodeHistoryError>`](crate::operation::list_lineage_node_history::ListLineageNodeHistoryError)
    pub fn list_lineage_node_history(&self) -> crate::operation::list_lineage_node_history::builders::ListLineageNodeHistoryFluentBuilder {
        crate::operation::list_lineage_node_history::builders::ListLineageNodeHistoryFluentBuilder::new(self.handle.clone())
    }
}