Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement support for retrieving arbitrarily-large record sets with p… #294

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

hfvr34
Copy link

@hfvr34 hfvr34 commented Feb 24, 2025

…aging

By default, the infoblox-ansible module will retrieve at most 1000 results, and silently discard the remainder. This can often be surprising and not what users intend. Trying to work around this limitation by setting large result-set sizes can also be resource intensive on both client and server.

Our underpinning Python library natively supports the use of paging; it defaults to off, but is relatively trivial to wire up.

This commit wires up a 'paging' boolean option in the infoblox provider, and defaults setting it to 'true'. It then passes this option to the underlying infoblox-client library.

#293

…aging

By default, the infoblox-ansible module will retrieve at most 1000 results,
and silently discard the remainder. This can often be surprising and not
what users intend. Trying to work around this limitation by setting large
result-set sizes can also be resource intensive on both client and server.

Our underpinning Python library natively supports the use of paging; it
defaults to off, but is relatively trivial to wire up.

This commit wires up a 'paging' boolean option in the infoblox provider,
and defaults setting it to 'true'.  It then passes this option to the
underlying infoblox-client library.

infobloxopen#293
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant