In AppFlow, include more options on describe_flow_execution_records

[mfnagato]

Describe the feature

The function describe_flow_execution_records currently returns all execution records of a flow.
Since starting flows from boto3 code is asynchronous, I'd like to start a flow but follow it up more efficiently using this function.
The suggested features would be to allow filtering by:

• executionId
• startedAt between 2 given timestamps (both optional)
• execution status

Use Case

I'd like to start a flow from boto3 code, like already available, but then follow it up more efficiently with the options described in the previous field for function describe_flow_execution_records .

Proposed Solution

As described in 1st field.

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

SDK version used

1.28.4

Environment details (OS name and version, etc.)

python 3

[tim-finnigan]

Hi @mfnagato thanks for reaching out. I looked at another issue involving these commands a while ago, there may be some overlap in your use cases: aws/aws-cli#6632

The AppFlow team owns the StartFlow and DescribeFlowExecutionRecords APIs which Boto3 and other AWS SDKs use. So we can forward feature requests like this to that team. If you have a support plan we recommend reaching out through AWS Support with requests like this. Otherwise we can reach out to the AppFlow team on your behalf. Please let us know.

[mfnagato]

Hi @tim-finnigan ,
I looked at the issue you mentioned, but I didn't find a request for improvement in describe_flow_execution_records. Can you forward the feature request to the appropriate team?

Thanks!

[tim-finnigan]

Thanks @mfnagato for following up. I've reached out to the AppFlow team for further feedback on this and created aws/aws-sdk#568 for tracking going forward. Please refer to that issue for future updates.