I'm currently writing my own modules to interface with my DNS provider, but
I'm running into some issues regarding some execution logic. The provider
currently has the following structure for their records: zone < zone domain
< zone domain record.
- zone is a container which logically holds all the domains and common
DNS records
- zone domain is a domain name
- ex: test.com
- zone domain record is a DNS record which relates to that domain.
- A record for www with 1.2.3.4 would create a DNS entry for
www..test.com
creation of these is easy using the create playbook here:
https://gist.github.com/analbeard/cb5913abfc6101b4eef88674853f3c16
However deletion is problematic. If you use the delete playbook at that
link, the first task will succeed and then the rest will fail due to to the
fact that the zone deletion also removes everything inside the zone
(domains and records). So, my question really is how would you expect that
to function? I can see some ways around this.
- I could add a force flag to the zone module which will only remove a
zone which is completely empty of domains/records if it isn't set tot true,
however in which case how should I handle attempted deletion of a zone with
contents but without force? Fail hard? Do nothing?
- I could allow the zone deletion to occur but then have the zone domain
/ zone record modules just pass successfully if the zone they're supposed
to be in doesn't exist?
What would be the best approach to this?
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/dec7ee06-2744-4203-9224-f190cb63a250%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
