You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 16, 2022. It is now read-only.
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: