Common configs for certificates: section

[IzumiSenaSora]

.lego.yml

accounts:
    noemail@example.com:
        acceptsTermsOfService: true
        keyType: EC384
        server: https://acme-v02.api.letsencrypt.org/directory
challenges:
    dns-01:
        dns:
            envFile: .env
            provider: cloudflare
            resolvers:
                - 127.0.0.1:53
certificates-default: &certificates-default
    account: noemail@example.com
    challenge: dns-01
    keyType: EC384
    profile: shortlived
certificates:
    example.com:
        <<: *certificates-default
        domains:
            - example.com
            - '*.example.com'
    example.net:
        <<: *certificates-default
        domains:
            - example.net
            - '*.example.net'
    example.org:
        <<: *certificates-default
        domains:
            - example.org
            - '*.example.org'
    example.me:
        <<: *certificates-default
        domains:
            - example.me
            - '*.example.me'
    example.c:
        <<: *certificates-default
        domains:
            - example.c
            - '*.example.c'
# --- Total 48 Domains --- Like this ---
hooks:
    deploy:
        command: './deploy.sh'
log:
    level: warn
storage: .

Can you add support to allow default option for all certs under 'certificates:' section like this

Details

certificates:
    account: noemail@example.com
    challenge: dns-01
    keyType: EC384
    profile: shortlived
    example.com:
        domains:
            - example.com
            - '*.example.com'
    example.net:
        domains:
            - example.net
            - '*.example.net'
# ---other domains ---

And for specific domain lets say i want to use dns-persist-01 challange then instead of adding all configs again it will only change what global config have

Details

certificates:
    account: noemail@example.com
    challenge: dns-01
    keyType: EC384
    profile: shortlived
    example.com:
        domains:
            - example.com
            - '*.example.com'
    example.net:
        challenge: dns-persist-01 # this one will try dns-persist-01 challange only others will use default dns-01
        domains:
            - example.net
            - '*.example.net'
# ---other domains ---

[ldez]

Currently, if there is only one account, he is used without explicit reference, same thing for the challenge.

https://go-acme.github.io/lego/advanced/file-configuration/index.html#smart-defaults

Additionally with the YAML inheritance, for now, I don't see a high benefit to increase the complexity of the configuration parsing by introducing global defaults.

Also, lego is in Go, a typed language, and certificates: is a map of certificate structure, I don't plan to introduce untyped/multi-typed elements.