Merge lp:~kiril-vladimiroff/cloud-init/cloudsigma-lack-of-ssh-key into lp:~cloud-init-dev/cloud-init/trunk
Proposed by
Kiril Vladimiroff
Status: | Rejected |
---|---|
Rejected by: | Scott Moser |
Proposed branch: | lp:~kiril-vladimiroff/cloud-init/cloudsigma-lack-of-ssh-key |
Merge into: | lp:~cloud-init-dev/cloud-init/trunk |
Diff against target: |
11 lines (+1/-1) 1 file modified
cloudinit/sources/DataSourceCloudSigma.py (+1/-1) |
To merge this branch: | bzr merge lp:~kiril-vladimiroff/cloud-init/cloudsigma-lack-of-ssh-key |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
cloud-init Commiters | Pending | ||
Review via email: mp+228331@code.launchpad.net |
Description of the change
Right now CloudSigma's datasource expects that the user will have defined ssh_public_key in his server context or at least that he will not delete the key (it's there by default for each user). If he does it however, the datasource can't get it, does not assume that this key could not be there and therefore the datasource does not work.
This merge proposal just fixes that issue :)
To post a comment you must log in.
Unmerged revisions
- 988. By Kiril Vladimiroff
-
CloudSigma data source should not rely on the existence of ssh_public_key
Hello, cloudinit. readthedocs. io/en/latest/ topics/ hacking. html .
Thank you for taking the time to contribute to cloud-init. Cloud-init has moved its revision control system to git. As a result, we are marking all bzr merge proposals as 'rejected'. If you would like to re-submit this proposal for review, please do so by following the current HACKING documentation at http://
I think this might be still valid, so please do re-submit.
Scott