Deployment Configuration

This section describes the configuration of the CLOE modeler. It is recommended to follow the configuration for the automated Terraform Setup. For the manual configuration of the build-pipeline see the Azure DevOps section below.

Terraform Setup

In the config file of the Terraform Setup you find the configuration for the CLOE modeler under the cloe_modules block:

modeler:
    deploy: true
    parameters:
      <env>: {}

The CLOE modeler does not require any additional parameters to be configured for the Terraform setup. Nevertheless, make sure to add <env>: {} for each environment to the config, where <env> is the key for your environment, e.g. dev - otherwise, the Terraform setup will not work.

Azure DevOps

Open your build-pipeline definition and change the following values:

1. Stage BuildCLOEArtifact:

   • Configure the highlighted parameters:

       template: /templates/generator/cloe.exec.cli.yml@templates # (1)
       parameters: # (2)
         cliArgs: |
           gen-sql \
             $(Build.Repository.LocalPath)/PATH_TO_MODEL \
             $(Build.Repository.LocalPath)/io \
             --output-sql-language "${{ parameters.outputSQLLanguage }}" \
             --update-existing-exec-sql-jobs \
             --output-mode "${{ parameters.outputMode }}"
         outputPath: '$(Build.Repository.LocalPath)/io'
         artifactPublishName: cloemodeler
   

   1. If you work in a customers DevOps you need to change the path to the CLOE Pipeline Templates Repository by changing the template path.
   2. If you do not use the recommended folder structure, you can change the path to the CLOE Model by changing the cliArgs. Just change the highlighted line to your CLOE model path.

2. Stage Commit:

   • Change the highlighted parameters:

     environment: '' # (1)
     artifactName: 'cloemodeler'
     commitToBranch: 'main' # (2)
     copyToPath: '' # (3)
   

   1. Specify the DevOps environment to be used e.g. "DEV".
   2. Specify the Branch on which you want to make your commits.
   3. Enter the repository path where the exec_sql JSON should be stored.