Problem/Motivation
Our Drupal site is autoscaled within the AWS framework and we are trying to use this module to help us manage content across instances. This works fine for basic content but has an issue with files, for instance, an image field on a content type.
When AWS deploys a new instance, it may not have that image file that the file entity points to, therefore, a user using this instance won't see that image when viewing that content type. I am using this module's drush commands during the deployment's "AfterInstall" script to add content that may not exist such as these files.
Proposed resolution
If you run an import for that content type, that particular piece of content isn't considered "changed" by this module, therefore it doesn't end up getting updated, which doesn't run an update on the file, which ultimately results in the image file never being added to that particular instance's public files folder so any user sent to that instance can't access that image. This is where a --force option on import would be helpful so that devs can force the module to update entities regardless of if they've actually been changed or not.
Another issue is that if I try to import just files to ensure they exist, this module attempts to delete all files that don't exist in the content sync folder. This is where having a --partial option would be nice where you can import/update all the content you have in your folder and just leave the content that exists in the database as is.