ryansb and sivel commented on your question onIRC but it sounds like you'd already left for the day. Here's what they said:
<abond> Good afternoon! I was wondering if someone could provide guidance on a design decision within the digital_ocean_domain module. I'm currently working with Akasurde to remove the `dopy` dependency within the DO modules so users can use Ansible out of the box. My original idea was to refactor the digital_ocean_domain module first keeping the same functionality as today. Second enhancement is to include the ability to add/edit domains <abond> I have a new PR https://github.com/ansible/ansible/pull/31765 to create a digital_ocean_domain_records module to add this functionality. Should I push to have this included in the current domain module or create a new module for domain records? <ryansb> Generally I'd say managing records is different from managing the domain <ryansb> so a new module seems like the way to go <sivel> +1 <ryansb> especially since lots of params wouldn't make sense f or both, e.g. "contact email" or whatnot <ryansb> or TTL. -- You received this message because you are subscribed to the Google Groups "Ansible Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to ansible-devel+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
