When we build the CM container, we set up import resolver rules so that if a blueprint imports a type file from the nexus3 raw repository, CM attempts to use a local copy, stored in /opt/manager/resources/onapspec in the CM container's file system, instead of accessing the nexus3 repo via HTTP.   CM does not appear to honor the import resolver rules and uses HTTP instead.   This will cause problems in deployments that do not have network access to the nexus3 repo.

This might be a result of moving from version 18.2.28 of Cloudify Manager to version18.7.23.  Possibly the mechanism for setting up the rules has changed, or possibly there's a bug in CM itself.

Note that the input resolver rules are set up in the get-type-files.sh script that runs when the CM Docker image is being built.  (dcaegen2/deployments/cm-container)