How will an Foglight upgrade affect standard, customized and newly created registry variables? (4351984)

How will an upgrade of Foglight Management Server (FMS) and cartridges affect my standard, customized, and newly created Registry Variables?

Registry variables are different from rules and are handled differently in terms of upgrade.

Foglight upgrades will replace new 'default' registry variable items and keep user modified registry variable items in regards to the new version coming down from the cartridge.

Examples to help illustrate:

1. Registry variable "foo" is defined in a cartridge with a global default that IS NOT changed from out-of-the-box setting: An upgrade of that cartridge that includes a new global default for the registry variable "foo" will update the value.
2. Registry variable "foo" is defined in a cartridge with a global default that IS changed from out-of-the-box setting: An upgrade of that cartridge that includes a new global default for the registry variable "foo" will NOT replace it (preserve user-edited values).
3. Registry variable "foo" has been modified to include a scoped 'Registry Value' in it: The scoped 'Registry Value' WILL remain after the upgrade (preserve user-edited values).

• Foglight does not create any backup copy of registry variables during an upgrade.
• It is not possible to rename a registry variables.
   

Q1: Do registry variables have a unique ID that the upgrade identifies like it does for rules?

A1. The name of a registry variable effectively acts as its ID

Q2. If the "Copy Registry Variable" option is used to copy a customized registry variable and then the "Delete This Variable" option to delete the original registry variable, will the upgrade create a new version of the original registry variable, thereby getting any new modifications to the registry variable coming from an upgrade?

A2. Yes. This will keep both the customized registry variable and a new registry variable with the original name coming down from a Foglight upgrade.