The field was labeled "Additional Hostnames" and described as names to include, but a list replaces the default names: the domain itself drops out, along with the wildcard on DNS challenges and the standard names on the others (build_domains in crates/common/src/network/acme/order.rs).
This renames the label to "Certificate Hostnames" and rewrites the description: the list replaces the defaults, what the defaults are, and how a name is read (no dot gets the domain added, a dot means as written). The property name and stored configs don't change, so nothing orders differently. Making the list additive would change what existing configs order, so it's left as is.
The schema was rewritten the way expr-schema.py writes it (checked byte for byte on the unchanged file first). The explain and explanation unit tests, which read the schema, pass; cargo build -p inbuxa and the fork checks are clean. The reference docs regenerate from this at release; the DNS guide's wording is in inbuxa/inbuxa.org (docs/certificate-hostnames-291).
Fixes #291.
The field was labeled "Additional Hostnames" and described as names to include, but a list replaces the default names: the domain itself drops out, along with the wildcard on DNS challenges and the standard names on the others (`build_domains` in `crates/common/src/network/acme/order.rs`).
This renames the label to "Certificate Hostnames" and rewrites the description: the list replaces the defaults, what the defaults are, and how a name is read (no dot gets the domain added, a dot means as written). The property name and stored configs don't change, so nothing orders differently. Making the list additive would change what existing configs order, so it's left as is.
The schema was rewritten the way `expr-schema.py` writes it (checked byte for byte on the unchanged file first). The explain and explanation unit tests, which read the schema, pass; `cargo build -p inbuxa` and the fork checks are clean. The reference docs regenerate from this at release; the DNS guide's wording is in inbuxa/inbuxa.org (docs/certificate-hostnames-291).
The field was labeled "Additional Hostnames" and described as names to
include, but a list replaces the default names: the domain itself drops
out, with the wildcard on DNS challenges and the standard names on the
others. Rename the label and say what the defaults are and how a name is
read. The property and stored configs are unchanged.
Fixes#291
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Fixes #291.
The field was labeled "Additional Hostnames" and described as names to include, but a list replaces the default names: the domain itself drops out, along with the wildcard on DNS challenges and the standard names on the others (
build_domainsincrates/common/src/network/acme/order.rs).This renames the label to "Certificate Hostnames" and rewrites the description: the list replaces the defaults, what the defaults are, and how a name is read (no dot gets the domain added, a dot means as written). The property name and stored configs don't change, so nothing orders differently. Making the list additive would change what existing configs order, so it's left as is.
The schema was rewritten the way
expr-schema.pywrites it (checked byte for byte on the unchanged file first). The explain and explanation unit tests, which read the schema, pass;cargo build -p inbuxaand the fork checks are clean. The reference docs regenerate from this at release; the DNS guide's wording is in inbuxa/inbuxa.org (docs/certificate-hostnames-291).