Creating a Release

NEW

The integration deployment process now involves creating a release, which is essentially a specific version of your integration flow. This functionality allows you to control and manage different versions of your integrations. Creating a release is mandatory before deploying an integration.

After completing the creation of your integration flow, you must:

Flow Status

The integration goes through three stages until deployment, which can be viewed next to Flow Status above the canvas:

• Unsaved: the flow has been modified but is not saved.
• Saved: the flow has been saved but does not have a release.
• Released: the flow has been saved and has a release.

NOTE

The release is a kind of snapshot of the integration flow. It is not possible to edit a release after its creation. If you need to make changes, you must create a new release.

Creating a release

To create a release of the integration flow, follow the steps below:

Viewing release history

To view the integration flow release history:

You will see a list with all created releases, including the following information:

• The release version number with an indication of those that are deployed.
• The username of who created the release.
• The release description.
• The release creation date.

In the "Actions" column, you can click the eye icon to see the release details or the trash icon to delete it.

NOTE

You can deploy the same release in the Staging and Production environments simultaneously.

Viewing and restoring a release

To view a release, click Release > Release History. Then click the eye icon in the "Actions" column on the corresponding release line.

When opening a release, the View Only label appears at the top of the screen. This indicates that you are viewing a specific version of the flow in read-only mode and cannot directly change the release.

You can switch between the Diagram and Source Code tabs to explore the release:

Diagram tab (read mode):

• Steps configuration forms with defined parameters and values.
• Existing subflows.
• Direct type routes.
• Resources files linked to the flow version.
• Variables (flow variables) and their settings in that release.

Source Code tab (read mode):

• Complete integration script in CAMEL YAML DSL format.
• Associated resources files and variables.

To restore the release, click RESTORE RELEASE.

After restoration, the flow will have the Unsaved status, allowing you to edit the integration again and create a new release.

IMPORTANT

If there are unsaved changes in the current flow, they will be lost when restoring the release.

Deleting a release

To delete a release, click Release History and then the trash icon in the "Actions" column.

You can only delete releases that are not deployed.

IMPORTANT

When deleting an integration flow that has created releases, all releases associated with the flow will be deleted. It is not possible to delete releases from flows that have at least one release with deployment history.