OptionalidAWS-assigned domain-name id (e.g. 75go78my1m). PRIVATE APIs only, where
v1 BasePathMapping addresses the domain by id rather than by hostname.
Held here rather than in a parallel array so the two cannot fall out of
step.
Stable slug naming this domain's base-path mapping resource.
Mappings used to be named by ARRAY POSITION — index 0 got
<api>-apigw-basepath-mapping, index 1 …-mapping-1. Every public API
listed the retiring api.coinfx.network first and the current api.cfx.to
second, so removing the first entry re-indexed the second one. Pulumi reads
that as a rename of a live mapping, and domainName is part of an
ApiMapping's identity (its import id is <mapping-id>/<domain-name>), so
the plan is a replace: it either fails on API Gateway's refusal to hold two
mappings for one domain+base-path pair, or takes api.cfx.to down while it
swaps. Across every public API at once.
Keying by slug decouples a mapping's identity from its neighbours, so dropping a domain plans exactly one delete.
NEVER derive this from name — that is an Output resolved from a
stack reference, and a Pulumi resource name must be a plain string known at
construction. Never derive it from position either; that is the bug above.
Renaming a slug replaces a live mapping.
Fully-qualified hostname, e.g. api.cfx.to.
One custom domain an API mounts on, plus the stable identity of the base-path mapping that binds them.