Skip to content
This repository has been archived by the owner on Feb 21, 2020. It is now read-only.

Environment-based default OSGi configurations #2

Open
davidjgonzalez opened this issue Sep 2, 2014 · 3 comments
Open

Environment-based default OSGi configurations #2

davidjgonzalez opened this issue Sep 2, 2014 · 3 comments

Comments

@davidjgonzalez
Copy link

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.)
@justinedelson
Copy link
Contributor

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])

?

@davidjgonzalez
Copy link
Author

@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.

@justinedelson
Copy link
Contributor

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants