packageeditor: How to use dependency properties and the Type field when creating superpackages

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

Type field potential values:

"ge" = greater than or equal to
"gt" = greater than
"le" = less than or equal to
"lt" = less than

Environment

• Release:
• Component: CAUIM
• distsrv probe

Resolution

"eq" = equal to the meaning of each is as follows: "eq" = only deploy the probe if the version being deployed matches the version installed.

"ge" = only deploy the probe if the version being deployed is greater than or equal to the version already installed.

"gt" = only deploy the probe if the version being deployed is greater than the version already installed. In both "greater than" cases it is expected that if a probe does not exist, it will be deployed, because technically installing any version of a probe that does not exist means that you are deploying a "greater" version.

"lt" = only deploy the probe if the probe being deployed is less than the version installed.

"le" = only deploy the probe if the probe being deployed is less than or equal to the version installed This is useful for downgrades - and it will not be expected to install the probe if it doesn't already exist, because installing any version of a probe is not "less than" no version. In some ways, it is useful to think that if a probe is not installed on a robot, then for the purposes of a superpackage it is similar to having version "0.00" of that probe installed.