Handling case-sensitivity when updating DNS records

[fuadsaud]

Hello!

• Vote on this issue by adding a 👍 reaction
• If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

I have a use case for updating a Cloudflare DNS record with the value output from an AWS Elasticbeanstalk environment's endpoint. The Beanstalk URL uses mixed case; however, it seems that Cloudflare ignores case and forces all values to be stored as lowercase values.

The consequence is that even if the Beanstalk endpoint hasn't changed, there will always be a diff between the desired state and the actual state on Cloudflare. This can be addressed by downcasing the value before passing it to the Record resource, but I'm wondering whether the resource itself should handle it; doing so would avoid surprise, semantically-irrelevant diffs.

Affected area/feature

Not sure.

[guineveresaenger]

Thank you for filing this issue @fuadsaud. Personally I feel that being explicit about these kinds of changes is a good default (what if Cloudflare's behavior changes?) but we'll take a look and discuss.