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

api/v3 Adding pagination functionality for supporting endpoints #40

Closed
wants to merge 5 commits into from
Closed

api/v3 Adding pagination functionality for supporting endpoints #40

wants to merge 5 commits into from

Conversation

corey-hammerton
Copy link
Contributor

If users want to be able to browse through the history available in
PuppetDB without crashing the server/client with too much information
adding attributes 'order_by', 'limit' and 'offset' to the following
functions:

nodes
facts
resources
reports
events
event_counts

If users want to be able to browse through the history available in
PuppetDB without crashing the server/client with too much information
adding attributes 'order_by', 'limit' and 'offset' to the following
functions:

nodes
facts
resources
reports
events
event_counts
Travis CI Build on this pull request filed due to trailing white-space
and under-indentation of newly modified code.

Details are https://travis-ci.org/puppet-community/pypuppetdb/builds/38442716
Travis CI build is still failing dur to under-indentation at the
lines where the event_counts function is declared.

Details are https://travis-ci.org/puppet-community/pypuppetdb/builds/38443403
@daenney
Copy link
Member

daenney commented Oct 20, 2014

Thank you for this! I've just started a new job so it's going to take me a few days before I can sit down to review it.

Including the order_by, limit and offset parameters to the function
fact_names. Documentation and tests show that it does support
the standard pagination functions
For the function calls and definitions where the parameter list is too
long and need to be appended to new lines, having each parameter in its
own line.

This standardizes the coding style and is compliant to python coding
best practices
@corey-hammerton
Copy link
Contributor Author

I will squash this pull-request into a single commit the next time I am able to work on it.

@daenney
Copy link
Member

daenney commented Jan 12, 2015

Alright. Looking forward to the rest.

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.

None yet

2 participants