GitHub user davidhalter opened a pull request:
https://github.com/apache/libcloud/pull/993
Add Cloudscale Host Keys And Documentation Improvements
## Add Cloudscale Host Keys And Documentation Improvements
### Description
This is a pretty small set of changes.
It only includes two things:
- We have had some issues where we added stuff like host keys to our API.
This should be reflected in Libcloud. Basically the default behavior is to
store all keys in the `extra` field that are not already part of the server
object.
- cloudscale.ch's name was never cloudscale. It's always written as the
full URL.
### Status
Done, ready for review
### Checklist (tick everything that applies)
- [x] [Code
linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
(required, can be done after the PR checks)
- [x] Documentation
- [x] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)
- [x]
[ICLA](http://libcloud.readthedocs.org/en/latest/development.html#contributing-bigger-changes)
(required for bigger changes)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/cloudscale-ch/libcloud cloudscale_host_keys
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/libcloud/pull/993.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #993
----
commit da059341ece564a8b0f04f53ca5e4a1e989e5649
Author: Dave Halter <[email protected]>
Date: 2017-02-24T12:12:11Z
Cloudscale Driver: Make it possible to list all things in the API that are
not part of libcloud.
We have had some issues where we added stuff like host keys to our api.
This should be reflected in Libcloud.
commit 4c5545c2296db10470239690c89307e24bc5da37
Author: Dave Halter <[email protected]>
Date: 2017-02-24T12:32:32Z
Change Cloudscale to cloudscale.ch.
This was not consistent in the libcloud documentation.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
