Commit Graph

8 Commits

Author SHA1 Message Date
neil
7362e8de4d fix format 2024-10-13 17:41:22 +02:00
Sergey Ponomarev
6b7b5caf54 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>
2024-05-18 12:06:41 +03:00
neil
c3a3d02bea fix https://github.com/acmesh-official/acme.sh/issues/3156 2021-01-10 11:48:12 +08:00
Ryan Meyers
38a8721a91 Escape opening brackets 2020-01-04 10:52:52 -06:00
Ryan Meyers
8aedf26a87 Replace \s with hard space 2020-01-04 10:51:32 -06:00
Phil Porada
6b817d4563 Set TXT record TTL to minimum possible value (#2465) 2019-09-05 22:15:28 +08:00
neilpang
227547f826 fix https://github.com/Neilpang/acme.sh/pull/1979 2019-01-30 20:13:23 +08:00
Aaron W. Swenson
c8c1140f15 Linode API v4 Redo
The Cloud and Classic Manager work with different APIs, and so require
a separate module, which we introduce here.

The README has also been modified to state that the two are separate
and incompatible, and provides instructions on using either.
2018-12-20 11:01:34 -05:00