[
https://issues.apache.org/jira/browse/JCLOUDS-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13674679#comment-13674679
]
Adrian Cole commented on JCLOUDS-110:
-------------------------------------
fyi, deleteZone doesn't return a taskId, so that one's a no-op.
<soap:Envelope
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";><soap:Body><ns1:deleteZoneResponse
xmlns:ns1="http://webservice.api.ultra.neustar.com/v01/";><result
xmlns:ns2="http://schema.ultraservice.neustar.com/v01/";>Successful</result></ns1:deleteZoneResponse></soap:Body></soap:Envelope>
> Update UltraDNS to latest server version (4.3.0)
> ------------------------------------------------
>
> Key: JCLOUDS-110
> URL: https://issues.apache.org/jira/browse/JCLOUDS-110
> Project: jclouds
> Issue Type: Improvement
> Components: jclouds-core
> Reporter: Adrian Cole
> Assignee: Adrian Cole
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> jclouds ultradns-ws provider is a bit behind latest ultradns code. It needs
> to be updated to support the following changes:
> from 4.3.0
> SOAP API A new optional element, forceOverlapTransfer, allows the
> movement of a territory between Directional DNS groups using a single
> transaction. This element is part of the addDirectionalRecord and
> updateDirectionalRecord requests. The element can be true or false; if a
> value is not supplied, it defaults to false. UMP-5874
> SOAP API The getResourceRecordsOfZoneResponse and
> getResourceRecordsOfDNameByTypeResponse requests now return resource records
> in the same order. UMP-5803
> SOAP API The getDirectionalDNSRecordsForHost parameter poolRecordType=0
> returns all Directional DNS records for the host. UMP-5873
> from 4.2.0
> SOAP API deleteZone returns taskId and runs as background task in the
> Customer Test Environment. UMP-5342
> from 4.0.0
> SOAP API The getLoadBalancingPoolsByZone now returns the record type
> (for example, PoolRecordType="A/CNAME") UMP-5320
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
