Environment-based default OSGi configurations
If runmode config folders are selected, provide option to pre-populate with common service configs
- Security checklist items
- Maintenance activities (WF cleanup, version purge, etc.)
For WF Cleanup, would it make sense to target only the DAM workflows? Something like:
Do you want to automatically purge DAM workflows? [yes] How many days of DAM workflows should be retained? [3](choices are [1,2,3,4,5])
?
@justinedelson If i picked No id still want (an option) to create the base WF sling:OsgiConfig node even if it was empty (just the pid and empty prop pairs)
IMO the inconvenient part is digging up the PIDs and creating the XMLs rather than configuring them.
I added DAM workflow purging in 0.0.10. The problem with creating an empty config is that this is a configuration factory. So there is no "empty" per se.