Struct AddServiceParams 

pub struct AddServiceParams<'a> {

    pub service_name: &'a str,
    pub exposure: &'a Exposure,
    pub auth: AuthChoice,
    pub enable_smtp: bool,
    pub enable_backup: bool,
    pub env_overrides: &'a BTreeMap<String, String>,
    pub enabled_groups: &'a BTreeSet<String>,
    pub registry_name: &'a str,
    pub repo_dir: &'a Path,
    pub pre_built_ctx: Option<BTreeMap<String, String>>,
    pub port_in_use: &'a dyn Fn(u16) -> bool,
    pub acme_mode: Option<&'a AcmeMode>,
    pub mode: PlanMode,
    pub port_overrides: &'a BTreeMap<String, u16>,
}

Inputs to add_service. One typed request instead of a positional argument list, so call sites (CLI today, other frontends later) name what they’re asking for and the retry path can’t drift out of sync with the original call.

Fields

service_name: &'a str

exposure: &'a Exposure

auth: AuthChoice

enable_smtp: bool

enable_backup: bool

env_overrides: &'a BTreeMap<String, String>

enabled_groups: &'a BTreeSet<String>

registry_name: &'a str

repo_dir: &'a Path

pre_built_ctx: Option<BTreeMap<String, String>>

When provided, its secrets and auth credentials are reused instead of generating fresh ones. Pass the context from the interactive prompt phase so the values the user saw match what gets written.

port_in_use: &'a dyn Fn(u16) -> bool

acme_mode: Option<&'a AcmeMode>

mode: PlanMode

port_overrides: &'a BTreeMap<String, u16>

Pin specific port assignments by name (e.g. {"http": 10005}) instead of running the allocator. Used by upgrade so a re-render preserves the install’s existing host ports — port_in_use would say they’re taken (the running service holds them) and the allocator would skip to the next free one.