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
In many apis, pagination is used to deal with lists of records (or record sets) beyond 100. After record 100, you'd need to pass a marker or the like to a new http GET operation. This is documented in Route53 and CloudDNS api guides
The problem causing issue #145 wasn't caught by our tests as we don't currently exercise providers enough to avoid latent pagination bugs. Pagination bugs render a provider completely useless. We need to add a mandatory test to ensure all providers can operate on realistically sized domains before being merged into denominator.
The text was updated successfully, but these errors were encountered:
In many apis, pagination is used to deal with lists of records (or record sets) beyond 100. After record 100, you'd need to pass a marker or the like to a new http GET operation. This is documented in Route53 and CloudDNS api guides
The problem causing issue #145 wasn't caught by our tests as we don't currently exercise providers enough to avoid latent pagination bugs. Pagination bugs render a provider completely useless. We need to add a mandatory test to ensure all providers can operate on realistically sized domains before being merged into denominator.
The text was updated successfully, but these errors were encountered: