Description
the merge option is only updating existing local modified files, but not adding new files from da
To Reproduce
Steps to reproduce the behavior:
- Go to your content in da.live
- Create 3 new files (test1, test2 and test3)
- import your content with aem content clone --path /your/path
- add another file (test4) in da.live
- change the document test1 and test2 in da.live
- change the file test2 and test3 locally
- you now have test1 updated in da, test2 updated in da and locally, test3 updated locally, test4 new in da
- execute aem content merge
- expected behavior: all changes from da are imported and in case of local changes merged
- current behavior: test1 is not updated locally (not expected), test2 and test3 has the diffs in the file (expected), test4 is not imported at all (not expected), so only files which have been modified locally are modified/updated
- See errorExpected behaviorA clear and concise description of what you expected to happen.
The only option which works for me to get new content from da.live is to use aem content clone --force --path ..., maybe updating the documentation that its more obvious that only locally modified files are updated and an option aem content pull would be nice
Version:
16.20.2
Additional context
The only option which works for me to get new content from da.live is to use aem content clone --force --path ..., maybe updating the documentation that its more obvious that only locally modified files are updated and an option aem content pull would be nice
Description
the merge option is only updating existing local modified files, but not adding new files from da
To Reproduce
Steps to reproduce the behavior:
The only option which works for me to get new content from da.live is to use aem content clone --force --path ..., maybe updating the documentation that its more obvious that only locally modified files are updated and an option aem content pull would be nice
Version:
16.20.2
Additional context
The only option which works for me to get new content from da.live is to use aem content clone --force --path ..., maybe updating the documentation that its more obvious that only locally modified files are updated and an option aem content pull would be nice