Update ListUsers.py to include Pagination in the Example #2178
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.
What does this PR do?
Add a line on pagination to the code example & clarifies that the USER_DATA_ATTRIBUTES_EMAIL needs to be set locally in order to populate (I think this is useful to note as while testing I kept running into this issue)
We have received multiple tickets in the past for customers confused on why when they run the below command:
curl -X GET "https://api.datadoghq.eu/api/v2/users" \
only 10 users users are returned.
The reason for this is that this command requires pagination.
I think having this in the snippet would help avoid these kinds of tickets.
Examples:
https://datadog.zendesk.com/agent/tickets/1753134
https://datadog.zendesk.com/agent/tickets/1363875
https://datadog.zendesk.com/agent/tickets/1090161
https://datadog.zendesk.com/agent/tickets/1470738
Additional Notes
Review checklist
Please check relevant items below:
This PR includes all newly recorded cassettes for any modified tests.
This PR does not rely on API client schema changes.
Or, this PR relies on API schema changes and this is a Draft PR to include tests for that new functionality.