Description of problem:
Certain puppet modules have multiple puppet module dependencies in order to function. Adding a puppet module with dependencies to a content view does not automatically add dependencies nor does it indicate to the user that there are dependencies they should be adding. This leads to a broken content view and broken deployments.

Version-Release number of selected component (if applicable):
6.0.7

How reproducible:
Always

Steps to Reproduce:
1. Add a puppet module with known dependencies to an existing or new content view.
2. Add operation completes without adding dependencies or providing warnings
3. Content view can be published successfully without adding dependencies.

Actual results:
No warnings

Expected results:
Automatically include dependencies (preferred), or provide warning (minimal)

Additional info:
puppet module install command resolves and downloads dependencies. We should provide at least equivalent functionality.
novice users cannot be expected to understand and search for dependencies
we provide no facility to examine the module code, analyse parameter requirements or dependency requirements.
low quality user experience around puppet
near zero documentation on using puppet in Satellite