ec2_snapshot_info add option for paginated requests

[abikouo]

SUMMARY

add new options max_results and next_token to read snapshot in paginated mode

#312

ISSUE TYPE

• Feature Pull Request

COMPONENT NAME

ec2_snapshot_info

ADDITIONAL INFORMATION

the following task will limit the number of snapshot returned in output

- name: limit snapshot to 50
  ec2_snapshot_info:
     max_results: 50
  register: snapshot_result

- name: read next 100 elements
  ec2_snapshot_info:
     max_results: 50
     next_token: "{{ snapshot_result.next_token }}"

[ansibullbot]

cc @jillr @s-hertel @tremble @willthames @wimnat
click here for bot help

[tremble]

For anyone else who sees this: this PR didn't change the results here, it's been this way since at least 2.9

Given support for 2.8 is about to be dropped I don't think it's worth adding a shim layer

[jillr]

The names of the new tasks should reflect what they are testing - in CI results we won't be able to see the code comments.

[abikouo]

The names of the new tasks should reflect what they are testing - in CI results we won't be able to see the code comments.

sure, I will update it
Thanks

[tremble]

Does it make sense to also require max_tokens to be set if next_token_id is set (so you can't set next_token_id if max_tokens isn't set)?

[abikouo]

Does it make sense to also require max_tokens to be set if next_token_id is set (so you can't set next_token_id if max_tokens isn't set)?

there are independent parameters.
if next_token_id is set and max_results is not set the max number of results will be 1000
when max_results is set alone, it is a way to start from the begining.

[abikouo]

@jillr could you please review and merge this if ok ? (integration tests have been updated as requested)