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

Improve naming of content sources created by esv2yaml

    XMLWordPrintable

Details

    • Task
    • Status: Closed
    • High
    • Resolution: Fixed
    • 1.0.0
    • 1.0.1
    • None
    • Platform162: Pre-GA2

    Description

      Currently, if esv2yaml processes /a/b/resource.xml, which contains nodes of category content at c/d1/e1, c/d1/e2 and c/d2, it produces /hcm-config/a/b/resource.yaml, as well as

      /hcm-content/a/b/resource.yaml
      /hcm-content/a/b/resource-1.yaml
      /hcm-content/a/b/resource-2.yaml

      Rather, the new content sources should be generated at

      /hcm-content/a/b/c/d1/e1.yaml
      /hcm-content/a/b/c/d1/e2.yaml
      /hcm-content/a/b/c/d2.yaml

      Attachments

        Activity

          People

            Unassigned Unassigned
            tjeger Tobias Jeger
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: