You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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_FILENov 8, 2024
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_FILENov 8, 2024
Welcome
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 asRFC2136_TSIG_FILE
which would be the path to the key file generated bytsig-keygen
?This way, lego would parse the file itself.
The text was updated successfully, but these errors were encountered: