You shouldn't have to include all the suggested modules. As you said, this just happened to one of your customers in the field. They probably gave a configuration that triggered it such as providing a HTTPS URL to connect to something. Your test plan may have overlooked that so there is a hole in the test plan. I'm going to assume that during your build routine, there is a scan of the code or read prepared file listing the dependencies. Sounds like you need to modify that to add the suggested ones to the top level dependencies list.