You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a problem for sls-mentor when using the command with the -t option (which allows to specify one or many tags to filter the resources with). In this case, IAM roles are left out of the analysis as they can't be retrieved by the listAllResourcesFromTags function, and are removed when making an intersection in listAllResources
Question 1: is this a bug or a feature ?
-> IMO it's a bug (because IAM Role can have tags so filtering makes sense, we just can't retrieve them using tags), but I'm open to contradiction there.
Question 2: if we try to fix it, what do we do?
A -> do not filter unsupported resources by tags at all (loses a bit the purpose, but easy)
B -> find another way to filter unsupported resources by tags (harder, but real fix)
Open to suggestions and contributions!
The text was updated successfully, but these errors were encountered:
AWS Tag editor does not support IAM roles.
https://docs.aws.amazon.com/ARG/latest/userguide/supported-resources.html
This is a problem for sls-mentor when using the command with the
-t
option (which allows to specify one or many tags to filter the resources with). In this case, IAM roles are left out of the analysis as they can't be retrieved by thelistAllResourcesFromTags
function, and are removed when making an intersection inlistAllResources
Question 1: is this a bug or a feature ?
-> IMO it's a bug (because IAM Role can have tags so filtering makes sense, we just can't retrieve them using tags), but I'm open to contradiction there.
Question 2: if we try to fix it, what do we do?
A -> do not filter unsupported resources by tags at all (loses a bit the purpose, but easy)
B -> find another way to filter unsupported resources by tags (harder, but real fix)
Open to suggestions and contributions!
The text was updated successfully, but these errors were encountered: