Support alternative Cloudflare API token file format

[naanlizard]

Small issue here, other services (letsencrypt and stuff using it) tend to use cloudflare's API key in the form of

# Cloudflare API token used by Certbot
dns_cloudflare_api_token = 0123456789abcdef0123456789abcdef01234567

https://certbot-dns-cloudflare.readthedocs.io/en/stable/

would it be possible to add support for that formatting so I don't need as many files kicking around?

Originally posted by @naanlizard in #668 (comment)

[favonia]

@naanlizard Thank you. I will have to think about this due to the additional complexity, and this feature might have lower priority on my list (sorry). On the other hand, I wonder if your true concern is the burden to maintain consistency across multiple configuration files, which I deeply sympathize! If so, I think tools like conf might help.

[favonia]

@naanlizard I wonder if you have tried the tool I suggested?

In the meanwhile, I might have come up with a good solution. I wonder if you are okay with writing a regular expression to identify the token? You will need to write a regular expression and the first submatch named token will be used as the API token. For example, the regular expression to use the whole file is

^(?<token>.*)$

Design question: the first config name that comes to my mind is ridiculously long: CF_API_TOKEN_FILE_CONTENT_REGEX

[favonia]

@naanlizard Hi, I have been trying various experiments and wonder how you feel about the design. BTW, I think the idea "first submatched named token" is overkill. It should just be "first numbered capture group". So the regular expression to match the whole file is just

^(.*)$

and it should probably be CF_API_TOKEN_REGEX for the whole file.

[naanlizard]

I'm sorry to be so quiet here - for the moment I can't play with this, but in a few weeks I'll be redoing one of my sites and can go in depth then!

[favonia]

@naanlizard I wonder if you have any new discovery?

[naanlizard]

I wasn't quite sure how to use those regex you provided, when I was reconfiguring things just now.

…

On Fri, Sep 13, 2024 at 5:22 AM favonia ***@***.***> wrote: @naanlizard <https://github.com/naanlizard> I wonder if you have any new discovery? — Reply to this email directly, view it on GitHub <#714 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABV4BWMNRFBYNRETJWRMB53ZWJR77AVCNFSM6AAAAABE2I2ZLKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBYGAYDKMJQG4> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[favonia]

@naanlizard Sorry but the feature was not ready yet. I was mostly only brainstorming.

[favonia]

@naanlizard I should elaborate: I thought you were planning to try out tools like https://github.com/kelseyhightower/confd that can synchronize multiple configuration files. Given my commitment to backward compatibility, I'd like to ensure we have a good design before implementing anything in the updater. Sorry for my miscommunication that made you think the feature was ready. I was hoping that you could join the conversation to help me pin down a good design.