Part 3 - Validation and deployment automation

Exercise 03 Version labels

Learning objective: Learn how to use version labels to deploy validated workflows to production.

You'll find the instructions to the exercises in the yellow annotations.

Warning - be considerate of other learners' projects and common spaces and workflows

The 05 Version Labels - Production space you will use for this exercise is shared with other course participants. Therefore, please do not modify any workflows or deployments that are not your own. Ensure your projects have unique names and that you do not overwrite anyone else’s work.

Exercise 03 Version labels

1. In the 03 Version labels folder, rename the project folder from 03_Pipeline_automated_validation_User_XX to 03_Pipeline_automated_validation_User_<your_user_id> (find your user ID in your space name). You will collaborate with other course participants in the same space 05 Version Labels - Production, therefore, your project name should be unique.

2. Upload this project folder to the 05 Version Labels - Production space on KNIME Business Hub

3. Create a version of 03_Pipeline_automated_validation_User_<your_user_id> workflow

4. Try to run the ad hoc execution with the Restricted EC (only for validated workflows) execution context

   • Execution should fail. Check the label assigned to the version: Auto-validation failed.

   • Navigate to the 01 Production data pipeline - Automated validation workflow and update it as indicated in the Secure authentication metanode

5. Once fixed, overwrite your workflow in the 05 Version Labels - Production space, create a new version, and try to run an ad hoc execution with the Restricted EC (only for validated workflows) execution context again.

   • Execution should succeed. Check the label assigned to the version: Auto-validation passed.