Skip to content

Commit 0659e4a

Browse files
Merge pull request #973 from penelopy/patch-6
W-18743165: Update package_convert.md
2 parents df224ee + 6088dc0 commit 0659e4a

File tree

1 file changed

+10
-12
lines changed

1 file changed

+10
-12
lines changed

messages/package_convert.md

Lines changed: 10 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,24 +1,22 @@
11
# summary
22

3-
Create a second-generation package version from a first-generation package.
3+
Convert a managed-released first-generation managed package into a second-generation managed package.
44

55
# description
66

7-
The package convert creates a new package in the Dev Hub if one does not already exist for the specified first-generation package.
7+
The package conversion command automatically selects the latest released major.minor first-generation managed package version, and converts it into a second-generation managed package version.
88

9-
It then creates a new package version in the Dev Hub with contents based on the specified first-generation package.
10-
11-
By default, the latest released non-patch version from the specified first-generation package will be converted. Use --patch-version to override the default. Read more about --patch-version option in help
9+
Use --patch-version to specify a released patch version.
1210

1311
To retrieve details about a package version create request, including status and package version ID (04t), run "<%= config.bin %> package version create report -i 08c...".
1412

15-
We recommend specifying the --installation-key to protect the contents of your package and to prevent unauthorized installation of your package.
13+
To protect the contents of your package and to prevent unauthorized installation of your package, specify the --installation-key flag.
1614

1715
To list package version creation requests in the org, run "<%= config.bin %> package version create list".
1816

1917
# examples
2018

21-
- Create a second-generation package version from the first-generation package with the specified ID and give it the installation key "password123"; uses your default Dev Hub org:
19+
- Create a second-generation managed package version from the first-generation managed package with the specified ID and give it the installation key "password123"; uses your default Dev Hub org:
2220

2321
<%= config.bin %> <%= command.id %> --package 033... --installation-key password123
2422

@@ -28,7 +26,7 @@ To list package version creation requests in the org, run "<%= config.bin %> pac
2826

2927
# flags.package.summary
3028

31-
ID (starts with 033) of the first-generation package to convert.
29+
ID (starts with 033) of the first-generation managed package to convert.
3230

3331
# flags.installation-key.summary
3432

@@ -68,20 +66,20 @@ Display verbose command output.
6866

6967
# in-progress
7068

71-
Request in progress. Will wait a total of %s more seconds before timing out. Current Status='%s'
69+
Request in progress. Will wait a total of %s more seconds before timing out. Current Status='%s'.
7270

7371
# flags.seed-metadata.summary
7472

7573
Directory containing metadata to be deployed prior to conversion.
7674

7775
# flags.seed-metadata.description
7876

79-
The directory containing metadata that will be deployed on the build org prior to attempting conversion.
77+
The directory containing metadata that will be deployed on the build org prior to attempting package conversion.
8078

8179
# flags.patch-version.summary
8280

83-
Specific released patch version to convert
81+
Specific released patch version to be converted.
8482

8583
# flags.patch-version.description
8684

87-
Specify a released patch version as major.minor.patch.build to convert to second generation package version
85+
Specify a released patch version as major.minor.patch to convert to a second-generation managed package version.

0 commit comments

Comments
 (0)