(GH-925) Fix pagination for auth0_organization_member import/Create limit #964
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🔧 Changes
Fix pagination for importing or creating
auth0_organization_member
to handle organizations with more than 50 members (Can't import or createauth0_organization_member
on Organizations with more than 50 members #925)This pull request aims to enhance pagination functionality for importing or creating
auth0_organization_member
by addressing organizations with more than 50 members. We're transitioning from offset pagination, which has a limit of 1000 entries, to checkpoint pagination to ensure efficient retrieval of organization members beyond this limit.Offset pagination retrieves data by specifying the number of items to skip and the number of items to return. However, its limitation of 1000 entries can lead to inefficient data retrieval for larger datasets. Checkpoint pagination, introduced here, offers a more efficient alternative, especially when dealing with a large number of organization members.
📚 References
auth0_organization_member
on Organizations with more than 50 members #925🔬 Testing
📝 Checklist