Uploaded image for project: 'Clamp'
  1. Clamp
  2. CLAMP-517 CLAMP Support new Control Onboarding flow
  3. CLAMP-568

Blueprint fields at microservice object level

XMLWordPrintable

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

      The blueprint field is currently stored at the Loop level, for the new self-serve control loop it must be supported at the microservice object level.

      So the java backend must be modified to support that.

      The hibernate entities must be changed but the existing blueprint field in loop should not be removed.

      Like the one in loop, this field should not be "exposed", as Yaml in json is not really appropriate.

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

              Created:
              Updated:
              Resolved: