You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: messages/package_pushupgrade_abort.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ Abort a package push upgrade that has been scheduled. Only push upgrade requests
4
4
5
5
# description
6
6
7
-
Specify the request ID for which you want abort the request. If applicable, the command displays errors related to the request. Only package push requests in Created or Pending statuses can be aborted.
7
+
Specify the request ID for which you want abort the request. If applicable, the command displays errors related to the request.
8
8
9
9
To show all requests in the org, run "<%= config.bin %> package pushupgrade list --package 033...".
Copy file name to clipboardExpand all lines: messages/package_pushupgrade_schedule.md
+14-1Lines changed: 14 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ To initiate a push upgrade for an unlocked or second-generation managed package,
9
9
For second-generation managed packages, the push upgrade feature is available only for packages that have passed AppExchange security review. To enable push upgrades for your managed package, log a support case in the Salesforce Partner Community.
10
10
For unlocked packages, push upgrades are enabled by default.
11
11
12
-
Use the –migrate-to-2GP flag to indicate you’re installing a converted second-generation managed package into an org that has the first-generation managed package version of that package installed.
12
+
Use the -–migrate-to-2GP flag to indicate you’re installing a converted second-generation managed package into an org that has the first-generation managed package version of that package installed.
13
13
14
14
# flags.target-dev-hub.summary
15
15
@@ -27,10 +27,22 @@ ID (starts with 04t) of the package version that the package is being upgraded t
27
27
28
28
Date and time (UTC) when the push upgrade is processed. Set to the earliest time that you want Salesforce to attempt to start the upgrade.
29
29
30
+
# flags.start-time.description
31
+
32
+
Scheduled push upgrades begin as soon as resources are available on the Salesforce instance, which is either at or after the start time you specify. In certain scenarios, the push upgrade starts a few hours after the scheduled start time.
33
+
34
+
As a best practice, schedule push upgrades at off-peak hours like 1:00 AM Saturday.
35
+
If you don't specify this flag, the push upgrade is scheduled to run as soon as resources are available on the Salesforce instance.
36
+
30
37
# flags.org-file.summary
31
38
32
39
Filename of the CSV file that contains the list of orgs that need the package upgrade.
33
40
41
+
# flags.org-file.description
42
+
43
+
The file must contain one org per line. The org ID must be the only value in each row.
44
+
All listed orgs must have a package version installed in their org that is lower than the package version you specified for the --package-version flag.
45
+
34
46
# flags.org-list.summary
35
47
36
48
Comma-separated list of subscriber org IDs that need the package upgrade.
@@ -94,3 +106,4 @@ Package Version Id
94
106
# output
95
107
96
108
Push upgrade has been scheduled. To check the status of this push upgrade, use push upgrade request ID [%s] with either "package push-upgrade list" or "package push-upgrade report".
0 commit comments