Uploaded image for project: '[Read Only] - Hippo Configuration Management'
  1. [Read Only] - Hippo Configuration Management
  2. HCM-41

Provide a solution for nodes ordered by hippo:sequence during migration

    XMLWordPrintable

Details

    • New Feature
    • Status: Closed
    • Normal
    • Resolution: Fixed
    • None
    • None
    • None
    • 3
    • Platform Sprint 152

    Description

      The current ESV bootstrap configurations sometimes use hippo:sequence to ensure adding nodes in a specific order under a parent with orderableChildren=true.

      The migration tooling isn't (yet) capable of detecting this, nor catering for it, in case this happens across modules.
      Furthermore, if a parent has orderableChildren=true is 'unknown' as this is defined on CND level, which we do not (yet) parse.

      .meta:order-before is already supported, so technically this isn't 'a problem' for new configuration definitions after the migration (then this being a developer responsibility),
      and for the migration of the product (hippo) configuration this could be manually 'fixed', although already cumbersome. 
      But for migration of existing projects their configuration this really might become a hurdle.

      We must:

      • come up with a proper/generic (automated) solution, or
      • some kind of verification which at least flags or warns about possible wrongly ordered children, or
      • provide very clear upgrade instructions (and possibly additional tooling) allowing existing projects to verify/fix this manually

      Attachments

        Issue Links

          causes

          New Feature - A new feature of the product, which has yet to be developed. CMS-12967 Add yaml support to define a 'set' kind of property, having an unordered list of unique values

          • Normal - Normal priority, tasks to be done before next intermediate release
          • Open

          New Feature - A new feature of the product, which has yet to be developed. HCM-63 Add an optional .meta:ignore-reordere-children for nodes which child order can be ignored when detecting changes

          • Normal - Normal priority, tasks to be done before next intermediate release
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. CMS-12985 Extend support of .meta:order-before to ignore a missing sibling and/or accept a list of sibling names to evaluate

          • Normal - Normal priority, tasks to be done before next intermediate release
          • Open

          Improvement - An improvement or enhancement to an existing feature or task. CMS-12987 Remove unnecessary orderable from hippo product node types where feasible

          • Normal - Normal priority, tasks to be done before next intermediate release
          • Open

          Improvement - An improvement or enhancement to an existing feature or task. CMS-10667 Don't rely on pluginconfig/plugincluster JCR node ordering but use an explicit property to order by, if even needed

          • Normal - Normal priority, tasks to be done before next intermediate release
          • Closed

          Activity

            People

              Unassigned Unassigned
              adouma Ate Douma (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: