IAM crawlers do not process paginated results

[coryb]

Currently all the iam crawlers only process the first page of all these results:

ListAccessKeysResult
ListGroupPoliciesResult
ListGroupsResult
ListMFADevicesResult
ListRolesResult
ListUserPoliciesResult
ListUsersResult

They need to be checked and paginated using result.getIsTrunctated() and result.getMarker() then on the subsequent request call setMarker().

@e-gineer since you contributed the code, perhaps you could look into this? (or @ralph-tice since you were interested in these collections?) We don't use the iam collections at Netflix, so we have not noticed the problem, but Bob Brown on the edda-users ran into this issue.

-Cory

[e-gineer]

Sorry, I'm working on other areas at this time, and frankly my scala capabilities are limited to copy & paste coding of the other edda code. I just took a quick look, but don't see a simple path (in my capabilities) given the IAM user loop sets off multiple subcalls as well.

[hridyeshpant]

aws.stacks call is also showing only first 100 items.