Uploaded image for project: 'Clamp'
  1. Clamp
  2. CLAMP-516 loop through list of CL flow microservice to instantiate
  3. CLAMP-571

Camel route deploy-loop must support multiple blueprint deployments

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Medium Medium
    • Frankfurt Release
    • None
    • None
    • CLAMP-R6 Sprint 3

      This Camel route must now iterates on all microservice objects to  send mutliple queries to dcae to deploy the microservices in the right order (the one defined in the loop)

      The right input parameters from the globalPropertiesJson must be sent in the DCAE query.

       

      The dcaeDeploymentStatusUrl and dcaeDeploymentId must be updated accordingly in the new microservices object fields.

       

      Note: The approach could be to create a new Camel code on top of the existing deploy-loop flow as this one is already designedfor a simple blueprint (may be a copy of that code would have to be done). The code must be backward compatible, meaning that a blueprint containing multiple microservices should still work

       

            xuegao xuegao
            sebdet sebdet
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: