Details
-
New Feature
-
Status: Open
-
Normal
-
Resolution: Unresolved
-
None
-
None
-
None
Description
Follow up from HCM-121
Provide a mechanism to automatically export certain JCR String values to resource files with appropriate filenames, rather than including the values in-line in the configuration or content YAML. The most obvious candidate use cases would be Groovy upgrader scripts and HST templates embedded in config.
Note that auto-export will already update an existing resource file rather than re-embedding the new value, so this is only about creating new data. Thus it will require some kind of pattern to determine which values should be externalized.
