Upgrade objects

Command upgrade-objects can be used to upgrade objects to get rid of deprecated or obsolete data and configuration. This operation should be used with CSV output file from verify command. For more information about verification, see Verify.

By default, this command applies only verification items marked as type = seamless. It does not introduce new configuration; it only rewrites the existing obsolete constructs with their current forms.

Make sure you review the verification report before running the upgrade-objects command. It is important to understand what will be changed and how it may affect the system. For more information about verification, see Verify.

If no verification report is provided using the --verification-file option, the command displays a warning before applying any automatic upgrades. This warning can be suppressed using the --skip-upgrade-warning option.

By default, the upgrade-objects command upgrades objects stored in the repository.
Alternatively, you can use the --file option to upgrade objects from an XML file. This option does not require repository access, and it updates the original file in place with the upgraded object definitions.

The scope of the upgrade-objects command can be set using:

After selecting the objects to upgrade, you can further limit which verification items are applied by filtering them based on:

For details on these filtering categories, see Verify.

Verification of items can also be skipped using the last column in the CSV file. Set the column to any of the following values to skip the item: true, t, yes, or y.

Objects can also be upgraded partially. To exclude specific parts of an object (properties or containers), such as activation or description, from processing during the upgrade, use the -ei, or --exclude-item option.

The upgrade-objects command also supports multi-threading (-l, --multi-thread <NUMBER_OF_THREADS>). For more information, see how multithreading works.