Uploaded image for project: 'Hippo Configuration Management'
  1. Hippo Configuration Management
  2. HCM-134

Cannot specify or maintain content definition order within parent

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Top
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.0.1
    • Labels:
      None
    • Similar issues:
    • Story Points:
      1
    • Epic Link:
    • Processed by team:
      Platform
    • Sprint:
      Platform Sprint 158: Hardening, Platform161: Pre-GA1

      Description

      We seem to have overlooked a major/blocking requirement for content definitions: ordering within parent...

      We currently allow no meta-data on and within content definitions, nor delta/merge operations on them.
      Which now causes a major, and IMO blocking, issue as typically content definitions are orderable (hippostd:folder has orderable children).

      For example content under the root documents folder (/content/documents, of primary type hippostd:folder), which must be split per child node (as /content/documents is config, and child nodes are content), already causes this problem.

      We currently cannot support ordering a child node (separate content definition) /content/document/foo before /content/document/bar as we sort these alphabetically for processing/applying.
      And neither can we autoexport / define a reorder of such content definitions within the same parent path.

      So this imposes a structural/model issue which we somehow need to fix. And whatever the fix (and I'll have a few suggestions later), we're facing a change in both the current yaml definitions (or require something new/additional) and the storage model (baseline) and the model API...  

       

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              adouma Ate Douma
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: