Skip to content
This repository has been archived by the owner on Aug 16, 2022. It is now read-only.

Create Reference Implementation Paginated List + Detail Fetch #927

Closed
bbernays opened this issue May 19, 2022 · 0 comments · Fixed by #1000
Closed

Create Reference Implementation Paginated List + Detail Fetch #927

bbernays opened this issue May 19, 2022 · 0 comments · Fixed by #1000
Assignees

Comments

@bbernays
Copy link
Contributor

Many resources require multiple API calls to fully resolve one of the most common patterns is a paginated list call with a nested for loop to get the resource details. This can be very expensive in terms of time required to fully resolve a resource.

The following resources have implemented some type of parallelization to improve this:

  • aws_sagemaker_training_jobs
  • aws_ecs_task_definitions
  • aws_athena_data_catalogs

We should create a single reference implementation so that we can ensure we are catching all of the edge cases and also possibly implementing this in the SDK to reduce individual resource complexity

@bbernays bbernays linked a pull request Jun 3, 2022 that will close this issue
7 tasks
@bbernays bbernays self-assigned this Jun 8, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant