[MGNLCI-24] Default configuration should be to automatically import on Magnolia Install Created: 25/Jun/20  Updated: 25/Jun/20

Status: Open
Project: Content Importer
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major
Reporter: Christopher Zimmermann Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLCI-22 Bootstrapping/importing content with ... Closed
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)
Documentation update required:
Yes

 Description   

Please set 'magnolia.content.bootstrap.initial' to true by default.
This will then solve the problem reported by the original poster. And will make the content importer an improvement over the WEB-INF/bootstraps/common directory.

As to security concerns, the person who is setting up the entire Magnolia instance should be aware of what is in the content-importer specified directory at startup (Just as they are expected to be responsible for what is in WEB-INF/bootstraps/common directory). Otherwise they can set magnolia.content.bootstrap.initial to false.

Otherwise, (assuming this mode only runs at install of Magnolia, not every start.) It will be easy for people to miss the configuration and not get the desired bootstrapping, and they won't have another chance.


Generated at Mon Feb 12 00:22:40 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.