pub fn detect_manifest_path(
package_root: &Path,
override_name: Option<&str>,
) -> Result<PathBuf>Expand description
Locate a package’s manifest file inside package_root.
override_name lets a deploy entry select a non-default manifest file
(the manifest: field on a deploy PackageEntry) so one package can
ship per-deployment-target variants — e.g. package_manifest.yaml
(x86 + docker), package_manifest.jetson-native.yaml, and
package_manifest.jetson-docker.yaml, each with its own build/start —
without changing the manifest schema itself. When set, the named file
MUST exist (a typo’d target should fail loud, not silently fall back to
the default manifest and build the wrong thing). When None, the
default package_manifest.yaml (then legacy) is used as before.