Use the CLI to Install a Second-Generation Managed Package
Before you install a second-generation managed package (managed 2GP) in a scratch org, run this command to list all the packages and locate the ID or package alias.
sf package version list
Identify the version you want to install. Enter this command, supplying the package alias or package ID (starts with 04t).
sf package install --package "Expense Manager@1.2.0-12" --target-org jdoe@example.com
By default, the package install command provides admins access to the installed package. To provide access to all users, specify --security-type AllUsers when you run the package install command.
If you’ve already set the scratch org with a default username, enter just the package version ID.
sf package install --package "Expense Manager@1.2.0-12"
The CLI displays status messages regarding the installation.
Waiting for the subscriber package version install request to get processed. Status = InProgress Successfully installed the subscriber package version: 04txx0000000FIuAAM.
Control Managed 2GP Package Installation Timeouts
When you issue a sf package install command, it takes a few minutes for a package version to become available in the target org and for installation to complete. To allow sufficient time for a successful install, use these parameters that represent mutually exclusive timers.
-
--publish-wait defines the maximum number of minutes that
the command waits for the package version to be available in the target org. The default is 0.
If the package is not available in the target org in this time frame, the install is
terminated.
Setting --publish-wait is useful when you create a new package version and then immediately try to install it to target orgs.
- --wait defines the maximum number of minutes that the command waits for the installation to complete after the package is available. The default is 0. When the --wait interval ends, the install command completes, but the installation continues until it either fails or succeeds. You can poll the status of the installation using sf package install report.
sf package install --package "Expense Manager@1.2.0-12" --publish-wait 3 --wait 10
sf package install --package "Expense Manager@1.2.0-12" --publish-wait 6 --wait 10