-
Notifications
You must be signed in to change notification settings - Fork 725
IAMInstanceProfile and IAMInstanceProfileRole don't support tags #733
Comments
Hey @mavogel, I don't have write access to create branch and propose a fix for this though:
I'll fork and push a PR from there, sorry for the noise. |
I have built from master and executed a test locally with the change that you've merged and am still observing that only the Name property is filled up. The Tags aren't. Here's an example for a test environment (aws-nuke targeting
whereas with aws cli I can strictly observe that the Tags are there:
I am new to Golang so any help will be appreciated :) Thanks |
I dove into the details of why we the tags aren't obtained even though the fix was implemented and figured out that the Src: https://raw.githubusercontent.com/aws/aws-sdk-go/main/service/iam/api.go
I'll try to propose a fix for this later today. |
Closing the issue as the suggested fix was merged into master. 🎉 |
@svenwltr @der-eismann Is there a change to tag a 2.17.1 release with these changes incorporated as the 2.17.0 that was released doesn't have them? |
Description
I am having an automated script to remove IAM resources based on a specific tag.
In the config file I have the following filtering applied:
which works for
IAMRole
,IAMPolicy
, andIAMRolePolicyAttachment
but does not work forIAMInstanceProfileRole
andIAMInstanceProfile
.Unfortunately these two IAM resources don't support filtering by tag.
The actual error:
There is an enforced dependency when trying to remove global IAM resources. Hence, removing an IAM role won't work if
IAMInstanceProfile
andIAMInstanceProfile
haven't been removed previously.Can anyone help with this, please?
The text was updated successfully, but these errors were encountered: