Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update A records with changes, rather than overwriting them #28

Closed
wants to merge 1 commit into from

Conversation

rkday-pro
Copy link

This fixes #3 - I've tested it live.

This change doesn't make it possible for clients to choose whether they should overwrite or update a record - partly because I wasn't sure what a sensible API would be, and partly to be consistent with AAAA records (where changes always trigger an update).

Do you think offering this choice is necessary (or will it just be irrelevant once #8 is fixed, and deleted nodes remove themselves)? If you do, what do you think the API should be?

@lazypower
Copy link
Owner

@rkd-msw ah, I didn't notice this PR until just now. thanks for the contribution. I need to look deeper into why the CI tests are failing, it looks like the format has changed from what its expecting.

I'll set aside some time this evening to pull and review. Again, sorry about the delay

@rkday-pro rkday-pro closed this Jan 18, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Allow duplicate entries in Bind9 provider - dont alway's assume an update.
2 participants