[MAGNOLIA-758] Boostrapping of individual repositories Created: 02/Mar/06  Updated: 23/Jan/13  Resolved: 10/Nov/06

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: None
Fix Version/s: 3.0 Final

Type: Improvement Priority: Minor
Reporter: Markus Zingg Assignee: Philipp Bärfuss
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: 0.25d
Time Spent: Not Specified
Original Estimate: 0.25d

Attachments: Text File magnolia_bootstrap.patch    
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)
Date of First Response:

 Description   

Currently the boostrapping process affects all 4 repositories (website, config, users, userroles). If you want to boostrap for example only the config repository you have to delete all repositories so that the bootstrap process is triggered.

It would com in handy if the boostrapping process would check for the emptyness of every repository on its own and trigger the bootstrapping process for this repository alone (or every reopository which is empty).



 Comments   
Comment by Markus Zingg [ 02/Mar/06 ]

I created I small patch which solves this issue.

The patch has been made against the trunk version of magnolia revision 2083.

Comment by Philipp Bracher [ 10/Nov/06 ]

use the magnolia.bootstrap.ifEmpty property

In addition we should add a magnolia.bootstrap.force property (will create a new task)

Generated at Mon Feb 12 03:20:23 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.