Open habibimustafa opened 2 years ago
Taking a look into this now; it seems the get_droplet() func was the issue at first glance/running some debugging. It was only going to work if unique_name was true
. I will fix this and make sure I have ample tests around this so we no longer have that gap. TYVM for bringing this up!
Ran into this issue on 1.19.0, would be nice to have this fixed. Playbook registers as failed when you specify a firewall for a new droplet even though the droplet creation succeeds.
SUMMARY
When creating a new droplet with a firewall configuration, the new droplet still doesn't have a firewall.
ISSUE TYPE
COMPONENT NAME
community.digitalocean.digital_ocean_droplet
ANSIBLE VERSION
COLLECTION VERSION
CONFIGURATION
OS / ENVIRONMENT
STEPS TO REPRODUCE
EXPECTED RESULTS
a new droplet with 'web-server-fw' firewall created
ACTUAL RESULTS
a new droplet without any firewall created