Auto export improvements - Updater Editor Registry and Blueprints

as a developer I would greatly benefit the auto export to take the groovy scripts in the registry into account.

currently everytime a developer creates a new groovy script in the registry auto export either exports it to registry.yaml and or sequentialy registry-1.yaml registry-2... etc

As a developer the following structure would be great:

application

• config
  • configuration
    • update
      • registry
        • script1.yaml
        • script2.yaml
• content
  • configuration
    • update
      • queue
        • runonstartup.yaml

I've experimenten with this locally. By adding a new entry in the location mapper i got this working e.g.

        nodePatterns = new String[] {"/hippo:configuration/hippo:update/hippo:registry/" + NAME, "/hippo:configuration/hippo:update/hippo:registry/" + NAME};
        propertyPatterns = new String[] {"/hippo:configuration/hippo:update/hippo:registry/" + NAME};
        contextNode = "/hippo:configuration/hippo:update/hippo:update/hippo:registry/$1";
        file = "configuration/update/registry/$1.xml";
        ENTRIES.add(new Entry(nodePatterns, propertyPatterns, contextNode, file));

The other improvement is blueprints.

Currently the blueprints are being exported partially in configuration and partially in content. Due to the configuration of workspace in the auto export module.

I'd like blueprints to be exported only to configuration and preferably just 1 yaml file per blueprint. If it's more it's OK as well. As long as it is all in config.

In my project I managed to add the following entry in the auto export config to have this working:

/hst:hst/hst:blueprints/**: config

Thanks!