Versioning a Flow¶

A video below goes through the content of this section.

Now, let’s say that we want to change the scenario in the Flow so that it runs on a monthly basis, rather than when the underlying data sources are updated. To do this, we will:

• update the project on the Design node

• repackage the project into a new bundle version

• deploy the new bundle to the Automation node

Here are the detailed steps:

• Open the original project on the Design node. Navigate to the Scenarios tab and open the Rebuild data retrain model scenario.

• Turn off the existing trigger. Rather than deleting it, in case you want to switch back to this trigger later, click Add trigger, and select Time-based trigger.

• Name the trigger Monthly rebuild and retrain. Make the frequency of the trigger Monthly and have it set to trigger on the 1st of each month. Save your scenario.

• Navigate to the Bundles area. Click Create bundle and name it automation_v2.

• Leave a descriptive release note for your colleague in charge of the production environment, like Changed the scenario trigger to be monthly. These changes are now visible in the bundle’s commit log and diff tabs (accessible in the upper right), both here on the Design node and when the bundle is redeployed on the Automation node.

The following video goes through what we just covered.

Activate the New Bundle in the Automation Node¶

A video below goes through the content of this section.

• In the Automation node, navigate to the Bundles area and click Import bundle.

• Find the bundle you just created and import it.

• Select the automation_v2 bundle and activate it.

The project in production has been updated to execute on a monthly basis. You can check this by navigating to the Scenarios and seeing that the changes you made on the Design node are visible in the Automation node. If you need to roll back to a previous version, simply select that version in the Bundles area and activate it.

The following video goes through what we just covered.