Closed WesleyBatista closed 2 years ago
Thanks for the suggestion, the providers are implemented by different contributors, so the behaviors may be different from each other.
I'll look into the API docs of Cloudflare and try to create the subdomains instead of throwing out the errors.
Thanks a lot for implementing so fast! Works from my side :sparkles:
However, it creates the record with proxying disabled (I see it's the default when calling the API), thus the IP gets exposed, and I am still required going to the Cloudflare UI to enable record by record. It would be awesome if we had the option to instruct "proxied":true
For Linode provider we seem to support auto creation of subdomain if it does not exist (mentioned in the docs and implemented here), however for Cloudflare I currently get:
Error goes away once I manually create the
A
record fromCloudflare > DNS
UI, but I would like to manage everything as code. Would be cool having the same behavior as for Linode for Cloudflare as well.It would also be nice to have the non-existent subdomain in the error message so it saves one round of checking back in the code/configs which subdomain failed.