GitHub user teemuvesala opened a pull request:
https://github.com/apache/libcloud/pull/775
[LIBCLOUD-813] create record and update record was not working
## Create record and update record issues were fixed
### Description
Link to the bug report: https://issues.apache.org/jira/browse/LIBCLOUD-813
Following changes were required to get those working:
* Priority entry exists only at MX and SRV records
* Content type of submitted data had to be application/json
* Data parameter of connection request has to be string
Only MX and SRV records have pririoty. Cotent-type for data has to be json.
data param of connection request must be string, changed that.
### 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)
- [NA ] Documentation
- [X] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html) -
executed
- [ NA]
[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/teemuvesala/libcloud
LIBCLOUD-813-create-record-issues
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/libcloud/pull/775.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 #775
----
commit 1d1400981f6b97eb82fc810eeb86a1d03cda8e82
Author: Teemu Vesala <[email protected]>
Date: 2016-04-25T07:00:30Z
Following fixes were done: Only MX and SRV records have pririoty.
Content-type for data has to be json. data param of connection request must be
string, changed that.
----
---
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.
---
