[
https://issues.apache.org/jira/browse/LIBCLOUD-456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13841684#comment-13841684
]
Tomaz Muraus commented on LIBCLOUD-456:
---------------------------------------
I just remembered that object storage API uses a similar approach. It has two
methods instead of one (upload_object which takes a file path and
upload_object_via_stream which takes an iterator).
So in this case, proposed approach also makes sense from a consistency
perspective.
In any case, if more people firmly believe and have good reasons that a single
method is better than two methods, then I'm also opened to changing the
existing object storage API, but if we decide to do it, we should do it soon
(before 1.0 release).
> Promote methods for the SSH key pair management to be part of the base
> compute API
> ----------------------------------------------------------------------------------
>
> Key: LIBCLOUD-456
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-456
> Project: Libcloud
> Issue Type: New Feature
> Reporter: Tomaz Muraus
> Assignee: Tomaz Muraus
> Priority: Minor
>
> As discussed on the mailing list, promote key pair management methods to be
> part of the base compute API.
> This issue also includes updating all the existing drivers which currently
> expose key pair management through the extension methods to use a new
> standard API.
> Mailing list thread:
> http://mail-archives.apache.org/mod_mbox/libcloud-dev/201312.mbox/%3CCAJMHEmKOsFYJZDZQLb_Z2q1Rs8Ke%2B%2BxUNnqqEbPjyTccTgPYHQ%40mail.gmail.com%3E
> Proposed API: https://gist.github.com/Kami/7810989
--
This message was sent by Atlassian JIRA
(v6.1#6144)
