Per summary, the CF appliances should ship with the CLI tooling for all the providers CFME supports... at least those licenses might allow. This would include, at least all the other RH products, OSP, OSE, RHV. As a consultant, I'm often not able to access the clients network directly, the provided access through a clean windows laptop, VDI, or such. Installing the clients can range from a pain to impossible. Regardless, the appliances presumably have firewall access and the cli makes an quick and easy testing tool vs anything else.
+1
Dependency problems: (RPMs, Python packages, Ruby Gems, Ansible modules, etc.) Several of us on the platform team met recently to discuss dependency problems and came up with the following decisions: - The appliance will carry dependencies for the application and any necessary debugging tools - The application itself will declare all of its dependencies as it has in the past - Application plugins will declare their dependencies in a way that the application / appliance build code can aggregate and install them - Customer dependencies will need to be installed and maintained by customers since it is impossible for us to maintain and upgrade that list of dependencies. We can not guarantee that any changes to these dependencies will not break scripts that are not maintained by the engineering team. *** This bug has been marked as a duplicate of bug 1573658 ***