ContentPlugins » History » Version 1
Justin Sherrill, 11/23/2015 07:27 PM
| 1 | 1 | Justin Sherrill | h1. ContentPlugins |
|---|---|---|---|
| 2 | |||
| 3 | h2. What are they? |
||
| 4 | |||
| 5 | Adding the ability to install a new package onto the katello server and get a new content type (similar to pulp plugins). |
||
| 6 | |||
| 7 | |||
| 8 | h2. "Design" |
||
| 9 | |||
| 10 | * Content plugins are just foreman plugins that require katello |
||
| 11 | * Routes |
||
| 12 | * Plugin defines them |
||
| 13 | * Content registration defines them |
||
| 14 | * Top level nav |
||
| 15 | * add link |
||
| 16 | * provide UI |
||
| 17 | * Plugin would define |
||
| 18 | * Content type class |
||
| 19 | * association to repo |
||
| 20 | * migrations |
||
| 21 | * Restructuring Repository |
||
| 22 | * Use STI for diff repo types |
||
| 23 | * or use modules to insert code (less ideal, may get tricky with things like generating importers) |
||
| 24 | * Registration api for plugins to register the content type |
||
| 25 | * Plugin would define publish and promote acitons which accept as input view, version, & environment for which to publish or promtoe. These actions are registered via the plugin via api |
||
| 26 | * for Repo rabl, extend show using defined content rabl via plugin api |
||
| 27 | * UI Extension point for repo create & update/view |
||
| 28 | * Repository Enablement? |
||
| 29 | * Api For create repos (?) |
||
| 30 | * CVV details page |
||
| 31 | * Plugin defined tables for UI |
||
| 32 | * Lifecycle ENV page |
||
| 33 | * defails page |
||
| 34 | * content tables |
||
| 35 | * Repo apipie params |
||
| 36 | * allow plugins to add params |
||
| 37 | * Strategy |
||
| 38 | * Create multiple engines inline, tackle all contnet types for each 'plugable area' at a time and write/move to each engine. i.e. add registration endpoint and regitration for all content types, then add cv publish for all content types |
||
| 39 | * Plugin naming |
||
| 40 | * katello-rpm |