[SLING-7870] Adding FSRegistry based Content Deployment Handler Extension

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Component/s: Feature Model
• Assignee: Karl Pauls
• Reporter: Dominik Süß
• Created: 30/Aug/18 16:04
• Updated: 06/Sep/18 10:35
• Resolved: 06/Sep/18 10:35

Description

The current WIP of the feature model launcher provides a simplistic artifact handler feeding all artifacts into the Sling OSGi Installer to be processed.

To get to a more deterministic and layerable content deployment mechanism an extension should be written that satisfies the following requirements:

• uses Vault FSRegistry for prebuilding of package registry and precalulation of an execution plan
• works on top of a prefilled package registry (precaching)
• supports startorder to separate into separate executionplans that get executed in sequence
  • this allows to separate off a content base that gets fully installed ahead of any rest which allows prebuilding a precached repository that can be shared as starting point across instances

Issue Links

• is blocked by: SLING-7871 Add vault executionplan based package repository initalizer
• links to: GitHub Pull Request #15