CI deploymeent strategy questions

[pleusmann-conet]

Hi,

I am trying to implement a CI-Workflow using the scripts from this project to deploy our solutions and have a few questions regarding that:

1. Currently all pipelines are deployed using the modeler. I do not see them in the list resulting from 'vctl strategy get [...]'.
   1.1. Is that intentional?
   1.2. What will happen when I install the solutions again using vctl? Will it result in multiple instances and I need to delete the modeler-deployed instance first?
2. Some issued commands suche as `vctl tenant get-strategy' can only be triggered by admins. Our runtime user is no admin. any chance to run the scripts or at least achieve similar results without admin rights?
3. 'vctl scheduler stop pipeline-modeler' sometimes works, but very runs for a long time until the CI-pipeline times out. Why is that? Why does the pipeline-modeler has to be stopped anyway?

Would be great to get some help here.

Thanks,
Philipp

[cschuerings]

Hi Philipp,

1. Conceptually, the solution (including the pipelines) is uploaded and added to the currently assigned strategy of the tenant. You can use the command vctl tenant get-strategy <tenant_name> and vctl strategy get <strategy_name> -o json to check, which layers are in the strategy of the tenant.
   1.1. The correct command for listing all uploaded solutions is: vctl solution list. The pipelines itself are visible in the Pipeline Modeler (see 3).
   1.2. If you install a solution again, it will be uploaded, older versions of the solution will be removed from the tenant strategy and the new version will be added.
2. The CI strategy as described here targets a scenario, where the solution will be rolled out (installed) to a tenant. For this the tenant admin role is required.
3. The pipeline modeler needs to be restarted as changes to the tenant strategy only become visible after a restart of the application.

Best Regards
Christian