Bundle Selection and Builds

A staged deployment records desired component packages and options. Provider artifacts live in that deployment's .reploy/provider-store/; they are not shared through a hidden machine-wide Reploy store. Docker owns the resulting image and layer storage. The deployment state records the exact Docker image reference it currently uses.

Inspect the available component-qualified options and the current request:

reploy bundle options
reploy bundle list

Select or remove an option by its qualified name:

reploy bundle add application/imap
reploy bundle remove application/imap

Add or remove a direct package request from a specific component:

reploy bundle add-package application 'rich>=13'
reploy bundle remove-package application 'rich>=13'
reploy bundle add-package system jq

These commands update desired state only. They do not resolve packages or build an image. To build and fully validate the selected environment before running anything, use:

reploy build

Every newly created component layer is fully validated against the cumulative provider requirements. The last layer's evidence is also the resulting image's final validation evidence. --no-cache reruns resolvers and image construction instead of reusing the current verified build. Warm reuse of a mutable base-image tag accepts Docker's matching current local image without contacting the registry; use --no-cache when the operation must check the remote tag and rebuild from its current selection.

reploy up and reploy restart automatically reuse a current successful build or run the same build pipeline when it is missing or stale. Staged app commands, reploy shell, and reploy test require a current build. Staging and direct installation also ensure a current build before publishing the installation.

Remove deployment-local provider artifacts when they are no longer needed:

reploy bundle clean

Cleaning does not change the blueprint, request overlay, current build record, or Docker image. The current image remains runnable. A later build may need to download or reconstruct provider artifacts that were removed.

For deployments staged from remote refs, reploy stage --update refreshes the blueprint source according to its recorded reference. Package selection remains explicit in the deployment overlay.