Add zone export to API and flarectl#385
Merged
patryk merged 2 commits intocloudflare:masterfrom Nov 27, 2019
Merged
Conversation
... which implements the API endpoint described at:
https://api.cloudflare.com/#dns-records-for-a-zone-export-dns-records
... and exports a given zone's configuration in textual BIND format.
i.e. allow the following (presuming the right env vars are set)
to export the textual BIND configuration for the zone:
flarectl zone export --zone example.com > example.com.txt
patryk
approved these changes
Nov 27, 2019
|
Thanks! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
These two commits:
ZoneExportfunction to the API, which calls the proper API endpoint to return a textual BIND format dump of the given zoneflarectl, which in turn uses the aboveZoneExportAPI endpoint to dump the textual BIND format for the given zone to screen (or file, if input redirection is used).Provide a general summary of your changes in the title above. You should
remove this overview, any sections and any section descriptions you
don't need below before submitting. There isn't a strict requirement to
use this template if you can structure your description and still cover
these points.
Has your change been tested?
Locally, with a few zones and using both supported syntaxes:
Types of changes
What sort of change does your code introduce/modify?
Checklist: