Expand description
profile list — the ACME endpoints this configuration mounts.
The terminal’s half of GET /api/profiles. Both render
acme_proxy_admin::admin::render_profile_json, and they reach it from opposite
directions: the API describes a mounted acme_proxy_protocol::profile::Profile,
where this describes what the configuration on disk would mount.
That difference is deliberate rather than a shortcut. Building the real
thing means server::profile::build_all, which constructs every signer backend —
generating a CA key that does not exist yet, and contacting a relay’s
upstream — which is not a price a read-only listing should make an operator
pay. filter show already draws the same line, and it cuts both ways: the
panel is right about what is running, and this is the only one of the two
that can be pointed at a configuration the server would refuse to start on.