GitHub user tonybaloney opened a pull request:
https://github.com/apache/libcloud/pull/746
Fix minor bug in Dimension Data Backup driver
## Fix minor bug in Dimension Data Backup driver
### Description
Fixes bug in backup driver with incorrect field name in backup status
cc @jadunham1
### Status
Replace this: describe the PR status. Examples:
- done, ready for review
### Checklist (tick everything that applies)
- [ ] [Code
linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
(required, can be done after the PR checks)
- [ ] Documentation
- [ ] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)
- [ ]
[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/DimensionDataCBUSydney/libcloud trunk
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/libcloud/pull/746.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 #746
----
commit 0c3f6af4f7120fd0a44030bc468f590f711d98fe
Author: kumar Chockalingam <[email protected]>
Date: 2016-03-02T01:17:51Z
reordered the element creation to fix the issue when pool member is created
with the port
commit 5a5c25907e47fdc6f165508b44018616b209ea87
Author: Anthony Shaw <[email protected]>
Date: 2016-03-02T02:44:02Z
Merge pull request #10 from DimensionDataCBUSydney/fix-create-firewall-rule
reordered the element creation to fix the issue when pool member is câ¦
commit 2a3e9bdd1ade03db138c60a3e8d840f7687513b2
Author: anthony-shaw <[email protected]>
Date: 2016-04-13T09:28:53Z
Fix bug in Dimension Data backup driver missing field information
commit d75ad857ec8fea301038c78788e93526c3f74bf4
Author: anthony-shaw <[email protected]>
Date: 2016-04-13T11:37:21Z
Merge remote-tracking branch 'origin/trunk' into trunk
----
---
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.
---
