Uploaded image for project: 'Configuration Persistence Service'
  1. Configuration Persistence Service
  2. CPS-1639

Add trustLevel to CMHandle/dmi-registry

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Won't Do
    • Icon: Medium Medium
    • Montreal Release
    • None
    • None

      We want to update the state container in dmi-registry to have the trustLevel:

       

      container state {
        leaf cm-handle-state {
          type string;
        }
       
        leaf trustLevel { 
            type string; 
        }
      
       container lock-reason {
          uses LockReason;
        }
      
        leaf last-update-time {
          type string;
        }
      
        leaf data-sync-enabled {
          type boolean;
          default "false";
        }
      
        container datastores {
          uses Datastores;
        }
      } 

      trustLevel is an enum and like the cm-handle-state will be defined in Java

      The default trust level should be NONE

      The trustLevel should not be defineable as part of the CMHandle create endpoints e.g. cant create a CMHandle with trustLevel complete

      The trustLevel should be part of the body of a returned CMHandle

      The new dmi-registry should be uploaded using the model loader

      1. Meeting should be called with rest of team to decide:
        1. Do we add liquibase steps to remove the current dmi-registry and associated anchor
        2. Do we update model loader so that it removes the current dmi-registry

       

      A/C:

      Demo CMHandles are created with trustLevel NONE, get on CMHandle has the trustLevel in the body

       

            Unassigned Unassigned
            lukegleeson lukegleeson
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: