[
https://issues.apache.org/jira/browse/LIBCLOUD-681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14554495#comment-14554495
]
ASF GitHub Bot commented on LIBCLOUD-681:
-----------------------------------------
GitHub user smstone opened a pull request:
https://github.com/apache/libcloud/pull/526
[LIBCLOUD-681] Allow for multiple record changes in one call
Issue: https://issues.apache.org/jira/browse/LIBCLOUD-681
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/smstone/libcloud
LIBCLOUD-681_multiple_record_changes
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/libcloud/pull/526.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 #526
----
commit 0a7ddfd3484e47657f3fa81296e41f438fdcd7fc
Author: Steven Stone <[email protected]>
Date: 2015-05-14T14:57:57Z
[LIBCLOUD-681] Allow for multiple record changes in one call
commit ecac3db1e2b12c38ea2cc15c21b6ed6d5351b1f2
Author: Steven Stone <[email protected]>
Date: 2015-05-20T20:01:10Z
Tests for ex_bulk_record_changes
----
> Google DNS: Allow for multiple additions and/or deletions of Resource Record
> Sets in one call
> ---------------------------------------------------------------------------------------------
>
> Key: LIBCLOUD-681
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-681
> Project: Libcloud
> Issue Type: New Feature
> Components: DNS
> Reporter: Steven Stone
> Assignee: Eric Johnson
>
> Currently the {{libcloud.dns.drivers.google}} module only supports creating
> or deleting one DNS record at a time. It is very time consuming with the
> current {{create_record}} and {{delete_record}} methods to migrate a
> substantial amount of DNS records.
> The [Google Cloud DNS
> API|https://cloud.google.com/dns/api/v1beta1/changes#resource] supports
> sending multiple additions and/or deletions to resource record sets in one
> call, so there should be a corresponding method that supports this
> functionality.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
