As a user, I can see in logs that force_full option for sync or publish is enabled
It is possible that users configure importer/distributor to have force_full enabled and forget about it.
For example, Katello users can enable "force_full" sync or publish. This is usually done as part of debugging, but it's easy to set it and then forget to turn it off. The issue is not apparent until later on when there are performance issues with sync/publish.
Logging that force_full is used would help with debugging performance issues.
Log at INFO level and only when force_full option is set to True.
Message should specify the behavior the enabled option causes, e.g.:
- "fully resyncing due to use of force_full importer setting"
- "fully republishing due to use of force_full distributor setting"
#2 Updated by mhrivnak about 4 years ago
Agreed. This option changes the behavior of the task substantially, so I think it's reasonable to log at INFO. I suggest only logging a message when it is set to true, and focus the message on the behavior. Something like "fully republishing due to use of force_full setting".