GitHub user earthgecko opened a pull request:
https://github.com/apache/libcloud/pull/287
[LIBCLOUD-547] linode.py labels too long with name use linode id instead
Using linode["id"] for labels and the labels step needed to be moved down
to after the linode object exists so that the id can be used.
Apologies about the old commit messages could not get rid of them rebased
and all but the diff is sound.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/earthgecko/libcloud LIBCLOUD-547
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/libcloud/pull/287.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 #287
----
commit c2451f4e37f6823fec55fde00f88f1376eb3d999
Author: Gary Wilson <@earthgecko>
Date: 2012-05-31T17:50:36Z
IssueID #201 LIBCLOUD-201
zone.id changed to zone in lines 433 and 434
Modified:
libcloud/dns/drivers/zerigo.py
commit 6b45f6a5c188a1172c21da19e34cec026e447863
Author: Gary Wilson <@earthgecko>
Date: 2012-05-31T17:59:52Z
IssueID #201 LIBCLOUD-201
Restored original:
libcloud/dns/drivers/zerigo.py
commit db66910eec5f7d3d9046112c8cc73a12ec817b6f
Author: earthgecko <[email protected]>
Date: 2014-04-29T14:20:57Z
Merge branch 'trunk' of https://git-wip-us.apache.org/repos/asf/libcloud
into trunk
commit 664c858895de56c288c7681c5126c5b8a49da8e4
Author: earthgecko <[email protected]>
Date: 2014-04-29T14:49:46Z
Update trunk
commit 5fd94c90fd4d30c0f86fe54178930a4de1fc6152
Author: earthgecko <[email protected]>
Date: 2014-04-29T14:59:19Z
Update trunk
commit 94cb241141524329ccb279d8d54604e2be960901
Author: earthgecko <[email protected]>
Date: 2014-04-29T15:50:07Z
[LIBCLOUD-547] linode.py labels too long with name use linode id instead
commit 8d2931818bec45ce6e45f8bf44f2f0bb663be142
Author: earthgecko <[email protected]>
Date: 2014-04-29T16:08:59Z
[LIBCLOUD-547] linode.py labels too long with name use linode id instead
----
---
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.
---
