Configuration Packages

The VCS records enable data transfer from one instance to another in an automatic or semi-automatic way. You can import a configuration pack to avoid recreation of changes on every instance. This method ensures an easy update migration between instances.

For example, your team has created a new application on a development instance. Instead of copying the scripts and recreating all elements one by one manually, they assemble a configuration pack and import it to the production instance. While importing this pack into the target instance, the system checks the changes for possible collisions. This procedure ensures a stable process for the system update.

Configuration pack flow

---

tip

Role required: admin.

Good practice is to develop new applications and implement changes into existing ones on a separate instance. This reduces the number of possible mistakes and risks for everyday processes on the production instance. Therefore, the VCS records should be collected into one local pack within the relevant application.

There are two types of the packages:

• Local – to collect changes on the current instance.
• Retrieved – to apply the changes that were transferred from another instance.

The configuration management involves two main processes:

• Preparation and export of the configuration change – collecting the VCS records into a local pack on Instance #1, as a result the local pack changes its state to Completed and a SOP file is created.
• Import and deployment – uploading and deployment of the previously prepared configuration pack on Instance #2.