Skip to content

Deploy

Belt Deploy promotes changes between environments. A package is created in the source environment and then moves through testing and production deployment. This approach keeps the code identical across all environments.

Package

A package contains change files prepared in the current environment. Each package has a unique package_uuid. The identifier is preserved during import and subsequent export, so the promotion of one change is visible as a single chain.

Package information is grouped into one table row by package_uuid:

  • Package: the package identifier.
  • Import: the status of receiving and applying the package in the current environment.
  • Export: the status of preparing and sending the package to the next environment.
  • Action: the action available for the package's current state.

Environment Promotion

The typical package path is:

  1. Create an export package in the development environment.
  2. Download the package file and import it into the test environment.
  3. Verify the changes in the test environment.
  4. After testing, export the package from the test environment.
  5. Transfer the file to the production environment, then import and apply it.

The promotion path is development -> test -> production.

Statuses

  • applied: the package was successfully applied in the current environment.
  • sent: the export package was prepared and sent to the next environment.

Process Control

The package table shows import and export side by side, so one row shows the current stage of a package. Before transferring a package to the next environment, make sure it has been successfully applied and verified in the current one.