In addition to changing the values of configuration parameters, the configuration merge feature can create, modify, and delete dozens of different InterSystems IRIS objects, such as namespaces and databases, users, roles, and resource, and mirrors and mirror members, on both newly deployed and existing instances. This is done using the parameters in the [Actions] section, which is valid only in a merge file.
Do not add the [Actions] section directly to the Configuration Parameter File (CPF). The [Actions] section is not supported in the CPF, and causes instance startup to fail if included.
The operations specified in [Actions] are idempotent, meaning that they are executed only if they would result in a change — if an object to be created exists, an object to be deleted does not exist, or an object to be modified matches the specified change, the operation is skipped. The order of the operations in the [Actions] section of a configuration merge file has no effect on the order in which they are executed; InterSystems IRIS performs the operations in a deterministic order.
For complete information on the configuration merge feature, see Automating Configuration of InterSystems IRIS with Configuration Merge; for an explanation of how the [Actions] parameters are used and lists of the parameters and details about their usage, see Can configuration merge customize more than the configuration? and [Actions] Parameter Reference, respectively, in that document.