Right now, hammer-import stores a number of configuration-file YAMLs (interview_answers.yml, role_map.yml, config_macros.yml) in /etc/hammer/cli.module.d This means that executing the hammer command, for any reason, causes those files to be picked up and parsed. Would probably be better for them to live in their own place, rather than having them affect the general use of hammer itself.
Since this issue was entered in Red Hat Bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release.
email out to hammer-gurus asking for input
from email discussion with Tomas Strachota: "hammer searches for module configuration in /etc/hammer/cli.modules.d and loads it at startup to identify installed modules. It doesn't scan the directory recursively so a good place for module specific configuration you want to load later would be either /etc/hammer/cli.modules.d/import/ as you mentioned, /etc/hammer/import/ or something similar. You only have to avoid placing the files directly into cli.modules.d/." Let's move everything import-related to /etc/hammer/cli.modules.d/import
commit 0779db7ba5547525fa0a1411b18689a208830419
VERIFIED rubygem-hammer_cli_katello-0.0.4-14.el6sat.noarch rubygem-hammer_cli_foreman_tasks-0.0.3-3.el6sat.noarch rubygem-hammer_cli_foreman-0.1.1-16.el6sat.noarch rubygem-hammer_cli_import-0.10.2-1.2.el6sat.noarch rubygem-hammer_cli-0.1.1-12.el6sat.noarch all the configuration files shifted to /etc/hammer/cli.modules.d/import
shifting this to ON_QA as discussed in the email will be handled by @ggainey
verified with rubygem-hammer_cli_import-0.10.3-1
This was delivered with Satellite 6.0 which was released on 10 September 2014.