[MGNLCI-22] Bootstrapping/importing content with CT defined workspaces Created: 18/Nov/19 Updated: 04/Feb/21 Resolved: 25/Jun/20 |
|
| Status: | Closed |
| Project: | Content Importer |
| Component/s: | None |
| Affects Version/s: | 1.1 |
| Fix Version/s: | 1.0.3 |
| Type: | Improvement | Priority: | Major |
| Reporter: | Christopher Zimmermann | Assignee: | Robert Šiška |
| Resolution: | Fixed | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | 0d | ||
| Time Spent: | 1d | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||
| 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
|
||||||||||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||||||||||
| Epic Link: | LD improvements | ||||||||||||||||||||||||||||
| Sprint: | HL & LD 4, HL & LD 5 | ||||||||||||||||||||||||||||
| Story Points: | 5 | ||||||||||||||||||||||||||||
| Description |
|
Problem: If you use the Content Types feature to define workspaces and node types, and you have JCR content bootstrap files that rely on those Content Type definitions (typically in a modules 'mgnl-bootstrap' directory, or in the WEB-INF/bootraps/common directory), then the content will not be correctly installed at install time. When the system tries to bootstrap the content, it has not yet processed the Content Types and so the workspace does not exist yet. Implemented in this ticket: To bootstrap content, when using Content Types, use the Content Importer feature. Do not use the " WEB-INF/bootraps/common" feature. The following capabilities have been added to the Content Importer feature.
Note - if you use the bootstrap.initial property, then you will recieve additional import tasks at every system restart. You can workaround this by setting the property to false after the initial import. Or by removing the bootstrap files from the configured directory once they are imported.
Copied from a documentation comment from uscheidegger
|
| Comments |
| Comment by Robert Šiška [ 15/Jun/20 ] |
|
This issue implements:
.
|
| Comment by Christopher Zimmermann [ 15/Jun/20 ] |
|
And is something changed such that content imports succeed now when the workspace is created by a content-type? |
| Comment by Robert Šiška [ 15/Jun/20 ] |
|
Yes, content-importer has an optional dependency on content-type module, so when it starts, all repositories are already registered. |
| Comment by Christopher Zimmermann [ 16/Jun/20 ] |
|
So all changes are only relevant to the {{magnolia.content.bootstrap.dir }}directory (content importer), but not to the 'magnolia.bootstrap.dir' (usually 'WEB-INF/bootstrap/common')? |
| Comment by Christopher Zimmermann [ 16/Jun/20 ] |
|
So when magnolia.content.boostrap.initial=true is used - then on install, no Tasks are created, no human intervention required? (unless path already exists?) |
| Comment by Christopher Zimmermann [ 22/Jun/20 ] |
|
rsiska - When 'magnolia.content.bootstrap.initial=true' is used - does this happen at every startup? Or only at install as the 'WEB-INF/bootraps/common' feautre does? |
| Comment by Jaroslav Simak [ 25/Jun/20 ] |
|
Closing this ticket because module has been released even without proper final QA. |
| Comment by Robert Šiška [ 29/Jun/20 ] |
Yes.
Also yes.
Yes, at every start-up.
Yes, that's a problem but I'd say it's only a symptom of another problem that tasks are created even when there are no actual changes (see
That happens only with yaml files, right? There's an issue with DataTransporter ignoring Import Behaviour when importing yaml files... |
| Comment by Jaroslav Simak [ 29/Jun/20 ] |
|
rsiska |