[MGNLCI-7] Give developers additional flexibility to specify watched path Created: 06/Sep/16 Updated: 17/Jun/20 Resolved: 17/Jun/20 |
|
| Status: | Closed |
| Project: | Content Importer |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Story | Priority: | Neutral |
| Reporter: | Christopher Zimmermann | Assignee: | Unassigned |
| Resolution: | Obsolete | Votes: | 0 |
| Labels: | to-design | ||
| 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)
|
| Date of First Response: |
| Description |
|
Enable more sophisticated content import approaches by enabling users to use wildcards or perhaps regular expressions to specify which directories should be observed. For example, I would like to specify a path which would observe a certain subdirectory in each light module and only import those files. Something like: magnolia.content.bootstrap.dir=${magnolia.home}/../../../light-modules/*/imports
Maybe it would need to be an additional property to magnolia.content.bootstrap.dir, I dont know. |
| Comments |
| Comment by Robert Šiška [ 17/Jun/20 ] |
|
Implemented in |