libcloud-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tomaz Muraus (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LIBCLOUD-451) New ex_iamprofile feature in 0.14 beta doesn't work?
Date Tue, 03 Dec 2013 23:41:36 GMT

    [ https://issues.apache.org/jira/browse/LIBCLOUD-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13838336#comment-13838336
] 

Tomaz Muraus commented on LIBCLOUD-451:
---------------------------------------

Some people said that just bumping the API_VERSION variable should work and not break the
existing stuff, but I haven't tested it myself yet.

It would be great if someone could test and verify this and if that is indeed the case, make
the API_VERSION change.

> New ex_iamprofile feature in 0.14 beta doesn't work?
> ----------------------------------------------------
>
>                 Key: LIBCLOUD-451
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-451
>             Project: Libcloud
>          Issue Type: Bug
>          Components: Compute
>    Affects Versions: 0.14.0-beta3
>            Reporter: John Carr
>
> I got an unknown parameter error of some kind when testing the beta. It looks like our
API_VERSION is too old to support IAM profiles. I'm monkey patching it to the latest one in
my scripts now, which works for my use cases.
> It also uses isinstance(var, basestring) but on python2.7 that doesn't allow unicode
strings through because libcloud.utils.py3k.basestring isn't basestring. I don't know if that's
intentional, but it'd be good if it did accept unicode.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message