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

rfc2136: add support for a new environment variable RFC2136_TSIG_FILE #2329

Open
1 task done
datafoo opened this issue Nov 8, 2024 · 0 comments · May be fixed by #2330
Open
1 task done

rfc2136: add support for a new environment variable RFC2136_TSIG_FILE #2329

datafoo opened this issue Nov 8, 2024 · 0 comments · May be fixed by #2330

Comments

@datafoo
Copy link

datafoo commented Nov 8, 2024

Welcome

  • Yes, I've searched similar issues on GitHub and didn't find any.

How do you use lego?

Binary

Detailed Description

For the DNS provider rfc2136, rather that having to parse a key ourselves to extract the key name (i.e. RFC2136_TSIG_KEY), algorithm (i.e. RFC2136_TSIG_ALGORITHM) and secret (i.e. RFC2136_TSIG_SECRET), would it be possible to provide a new environment variable such as RFC2136_TSIG_FILE which would be the path to the key file generated by tsig-keygen?

This way, lego would parse the file itself.

@datafoo datafoo changed the title rfc2136: add support for a new environment variable RFC2136_TSIG_KEYFILE rfc2136: add support for a new environment variable RFC2136_TSIG_KEY_FILE Nov 8, 2024
@datafoo datafoo changed the title rfc2136: add support for a new environment variable RFC2136_TSIG_KEY_FILE rfc2136: add support for a new environment variable RFC2136_TSIG_FILE Nov 8, 2024
@ldez ldez self-assigned this Nov 8, 2024
@ldez ldez linked a pull request Nov 8, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging a pull request may close this issue.

2 participants