[
https://issues.apache.org/jira/browse/LIBCLOUD-676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14365094#comment-14365094
]
ASF subversion and git services commented on LIBCLOUD-676:
----------------------------------------------------------
Commit f4a149ec6a8b7478fdef645627b1bb445d189469 in libcloud's branch
refs/heads/trunk from [[email protected]]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=f4a149e ]
LIBCLOUD-676: Allow describing AMI tags
Removed filter that only allows returning tags for ec2 instances
Closes #482
Signed-off-by: Tomaz Muraus <[email protected]>
> ex_describe_tags shows results for instances only
> -------------------------------------------------
>
> Key: LIBCLOUD-676
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-676
> Project: Libcloud
> Issue Type: Bug
> Components: Compute
> Reporter: John Kinsella
>
> While AWS EC2 describe-tags API will return tags for any resource with tags,
> the libcloud ex_describe_tags() will not.
> Looking at the code, ex_describe_tags() calls ec2's DescribeTags with a
> filter of "'resource-type': 'instance'"
> I've looked through commits on ec2.py - I don't see a reason (historical or
> otherwise) for having ex_describe_tags not work on all ec2 resources?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
