Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support alternative Cloudflare API token file format #714

Open
naanlizard opened this issue Mar 17, 2024 · 1 comment
Open

Support alternative Cloudflare API token file format #714

naanlizard opened this issue Mar 17, 2024 · 1 comment
Labels
enhancement New feature or request low priority This is low priority next: design brainstorming The next step is to reflect upon the information and come up with a good design

Comments

@naanlizard
Copy link

naanlizard commented Mar 17, 2024

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 favonia changed the title cloud flare API key file format Support alternative Cloudflare API token file format Mar 17, 2024
@favonia
Copy link
Owner

favonia commented Mar 17, 2024

@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 favonia added next: design brainstorming The next step is to reflect upon the information and come up with a good design low priority This is low priority enhancement New feature or request labels Mar 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request low priority This is low priority next: design brainstorming The next step is to reflect upon the information and come up with a good design
Projects
None yet
Development

No branches or pull requests

2 participants