I am creating packages to sync our AEM prod environment with dev using package manager. Since package manager fails to build the packages with large size, I was splitting some folders by creating packages for the sub-folders inside the larger folders. But as there is many number of sub folders, it is a burden to create packages for each one. So, I decided to create packages by taking multiple sub-folders inside the larger folder. For that I gave regular expressions in filter rules like following;
include | /content/dam/portfolio/properties/f* |
include | /content/dam/portfolio/properties/g* |
include | /content/dam/portfolio/properties/h* |
What I meant with this is to take all the sub-folders starting with f, g, and h inside /content/dam/portfolio/properties/ folder.
But this is not working as expected. What is the correct solution to achieve my requirement?
Solved! Go to Solution.
Views
Replies
Total Likes
The subfolders must be direct children of the filter root, or you should allow all parent folders up to the filter root [0]. Additionally, make a slight adjustment to the include regex by using f.*, g.*, etc.
[0]: https://jackrabbit.apache.org/filevault/filter.html#usage-for-export
Hi,
Keep in mind that the include and exclude rules accept only regular expressions. Therefore, I believe that might be the issue. You can try something similar to the following, which will include only the folders which start with the letter "f" under the path "/content/dam/portfolio/properties"
/content/dam/portfolio/properties/f[^/]+.*
Here you can find more info: https://jackrabbit.apache.org/filevault/filter.html#Include_and_Exclude_Elements
Hope this helps
The subfolders must be direct children of the filter root, or you should allow all parent folders up to the filter root [0]. Additionally, make a slight adjustment to the include regex by using f.*, g.*, etc.
[0]: https://jackrabbit.apache.org/filevault/filter.html#usage-for-export
If content sync is a regular activity, please review https://adobe-consulting-services.github.io/acs-aem-commons/features/contentsync/index.html
Its a new content sync feature in ACS commons to incrementally sync content