Delete a AWS IAM user via IAMbic fails when user has access keys

[smoy]

Describe the bug
Delete a AWS IAM user via IAMbic fails when user has access keys

To Reproduce
Steps to reproduce the behavior:

1. Create a AWS IAM user with active access keys
2. Change the IAM user template, deleted: true
3. iambic apply
4. See error

Expected behavior
The targeted IAM user should be deleted successfully.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• v 0.9.8

Additional context
AWS IAM control plane refuse to delete the IAM user if it has access key. So the delete action needs to be multi-part, first remove the access keys, before deleting the user.

In additional, the IAMbic tool should surface this type of apply error. Currently, it's difficult to pinpoint it without a cloud trail investigation.

Community Engagement
Your vote counts! Please support this bug report by adding a 👍 reaction to the original issue, which will aid the community and maintainers in addressing this problem.

Please refrain from adding "+1" or "me too" comments, as these create unnecessary noise for issue followers and do not help in prioritizing the issue. If you wish to contribute to solving this issue or have submitted a pull request, please leave a comment.

[datfinesoul]

In regards to 4, in the steps to reproduce, the error message was not clear that this was happening.

Proceed? [y/N]: y
2023/06/21 06:16:15 [info     ] Applying changes to resource.  
  accounts=[
    "management - (000000000000)"
  ] 
  resource_id=myuser 
  resource_type=aws:iam:user
2023/06/21 06:16:17 [error    ] Error encountered when removing resource changes. 
  accounts=[
    "management - (000000000000)"
  ] 
  resource_id=myuser 
  resource_type=aws:iam:user
2023/06/21 06:16:17 [info     ] Finished applying changes.

Finding this was only possible when digging into the CloudTrail DeleteUser event.

[2bytechef]

I can take a crack at this bug if you wouldn't mind assigning it to me

[smoy]

@Wilhite-r I haven't seen any movement in this issue. Would you mind if I assign this to another developer?