resource/aws_iam_user: Delete a user's virtual MFA devices when force_destroy is enabled #11040
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.
Fully removing a virtual MFA device requires first deactivating then deleting it. Currently the resource
aws_am_user
withforce_destroy = true
implements only the deactivation step and results in dissociated virtual MFA devices being left behind. This can cause issues should a future user - likely one with the same name as the deleted user - attempt to enable virtual MFA with the same path.This PR implements the deletion step for virtual MFA devices. It also renames the prior function
deleteAwsIamUserMFADevices
todeactivateAwsIamUserMFADevices
in order to reflect what's actually happening to non-virtual MFA devices.Community Note
Release note for CHANGELOG:
Output from acceptance testing: