SystemPackage - deleteAllHiddenSysPacks
SystemPackage - deleteAllHiddenSysPacks
Description :
This command deletes all the hidden system packages in the system, along with the jobs that created them.
- About hidden system packages ***
Each time you run the deprecated Provision : provisionDevice command, the system creates a "hidden" system package. This package reflects the original system package plus the contents of the input file you passed in with the provisionDevice command.
Here is a scenario to explain hidden system packages:
1. Suppose you run the deprecated provisionDevice command and specify the job name of Job1.
2. Start the console (GUI), navigate to the Jobs folder and display the System Package Properties tab for Job1.
3. The "Path to system package field" displays the system package on which the job is based. However, because you used the deprecated provisionDevice command to create a job, this command creates a "hidden" system package.
You can tell that this is a hidden system package because:
-- The system package name is an automatically generated name made up of the base system package name with a random number appended. Example: redHat5_132736545.
-- If you look at the system packages under the Depot, you will NOT see this hidden system package listed in the Depot along with the regular, exposed system packages.
Best practice: We recommend that you manage these hidden system packages so they do not clutter your database. Here are some management options, using various commands in the SystemPackage namespace:
-- If you know you do not want these hidden system packages, simply run the deleteAllHiddenSysPacks command. This command deletes all the hidden system packages AND all the jobs that created those hidden system packages.
-- If you want to delete some hidden system packages, but not all of them, first run the listAllHiddenSysPacks command. For each hidden system package, this command displays the following output:
DBKey_of_hidden_sys_pack, name_of_hidden_sys_pack, [job_associated_with_hidden_sys_pack]
(The job associated with the hidden system package does not appear if you have already deleted the job.)
Using this output, you can then run the deleteSysPack command and specify the DBKey of the specific hidden system package you want to delete.
Best practice: Clean up hidden system packages when you clean up old Provision Jobs. Whenever you delete unused Provision Jobs, it is a good idea to clean up their associated hidden system packages, by using the management options listed above.
Return type : String