[MGNLCI-21] Content importer can handle YAML bootstraps with media files Created: 04/May/20 Updated: 04/May/20 |
|
| Status: | Open |
| Project: | Content Importer |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Story | Priority: | Neutral |
| Reporter: | Christopher Zimmermann | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Release notes required: |
Yes
|
| Documentation update required: |
Yes
|
| Epic Link: | LD improvements |
| Description |
|
As a developer I want to import YAML bootstraps that include (or reference) binaries so that I can get assets or other sophisticated content imported. Notes: Hopefully the YAML handling will store the binaries as separate files, not as inline in the YAML. Separate files for binary would also be much nicer to browse the content, and easier to set up content importing of media files. |