Discover and install packs
After adding a source, list available packs and preview the change before writing files.
Discovery recommends an install command when packs are available. After a successful install, Luna recommends checking for updates, updating installed packs, or uninstalling the pack. A dry run shows only its plan.
luna discover
luna install dotnet-project --dry-run
luna install dotnet-project
Use id@version to choose an exact release:
luna install [email protected] --dry-run
The dry run resolves the pack and preflights the target changes without
modifying project files or LunaPack state. It asks for every configurable pack
parameter before planning so conditional references, files, hooks, and sources
reflect the selected values. For a noninteractive preview, add
--skip-parameters. Luna still uses declared defaults, variables, composite
bindings, and explicit --parameter values; the preview fails when a required
parameter remains unresolved. Remove --dry-run when the plan is ready to
apply.
Pass --prompt-parameters on a real install to answer every configurable
parameter instead of only unresolved required parameters. Optional prompts
offer their declared defaults.
Read the Result
Dry runs group source changes, managed-file actions, and lifecycle actions under labeled sections. Their ASCII action markers remain meaningful when terminal color is unavailable. Lifecycle script details also identify whether policy, command arguments, persisted trust, or confirmation controls consent.
A successful install lists its managed-file changes. Use
--no-file-change-output to hide that list in routine or automated runs. This
option does not hide managed-file actions from --dry-run.
If the selected pack ID and version exist in multiple configured sources, both the dry run and successful install identify the chosen source by name and type. The earliest configured source wins an equal-version tie.
Continue from the basic install
- Use parameters and variables when a pack asks for values.
- Review lifecycle hooks before allowing pack-provided scripts.
- Use target remapping for repository-specific locations.
- Follow external-source approval when the preview proposes additional Git sources.
- Use adoption only for existing files that exactly match pack content.
The command reference lists every install option and interaction.