Commit Graph
8 Commits
  • dns_easydns: match the TXT record by its rdata when removing (#7199)
    dns_easydns_rm() picked the first id in the search response and ignored
    $txtvalue. When two challenge records exist under the same host - for
    example when example.com and *.example.com are issued as separate
    certificates - a concurrent run's record could be deleted instead of
    our own.
    
    Select the record by its rdata instead, following the dns_cf.sh
    convention of matching name + value. tr '{' '\n' puts one record per
    line, so both _egrep_o branches - egrep -o and the BRE sed fallback -
    return the same single id. Without it the sed fallback would return
    only the last match, since .* is greedy.
    
    An empty record_id is now treated as "nothing to remove" and returns 0,
    rather than being reported as an error.
    
    Also add the credential check that _rm was missing. It deliberately
    does not call _saveaccountconf_mutable, as _add already does that.
    
    Co-authored-by: wurzelpanzer <wurzelpanzer@maximolider.net>
  • DNS provider API: structured description
    Instead of using comments declare info in a special variable.
    Then the variable can be used to print the DNS API provider usage.
    The usage can be parsed on UI and show all needed inputs for options.
    
    The info is stored in plain string that it's both human-readable and easy to parse:
    
        dns_example_info='API name
         An extended description.
         Multiline.
        Domains: list of alternative domains to find
        Site: the dns provider website e.g. example.com
        Docs: Link to ACME.sh wiki for the provider
        Options:
         VARIABLE1 Title for the option1.
         VARIABLE2 Title for the option2. Default "default value".
         VARIABLE3 Title for the option3. Description to show on UI. Optional.
        Issues: Link to a support ticket on https://github.com/acmesh-official/acme.sh
        Author: First Lastname <authoremail@example.com>, Another Author <https://github.com/example>;
        '
    
    Here:
    VARIABLE1 will be required.
    VARIABLE2 will be required too but will be populated with a "default value".
    VARIABLE3 is optional and can be empty.
    
    A DNS provider may have alternative options like CloudFlare may use API KEY or API Token.
    You can use a second section OptionsAlt: section.
    
    Some providers may have alternative names or domains e.g. Aliyun and AlibabaCloud.
    Add them to Domains: section.
    
    Signed-off-by: Sergey Ponomarev <stokito@gmail.com>
  • easyDNS API out of beta
    Added new links to API docs and API access signup