Document URL: 

Currently me pointing to Sat6.1 link
https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.1/pdf/User_Guide/Red_Hat_Satellite-6.1-User_Guide-en-US.pdf

Section Number and Name: 9.1 Installation Step 5)

Precisely this step needs to be expanded in more detail for the workflow changes. 
"Import the puppet classes and associate them with specific environments."

Describe the issue: Changes required **only** for Satellite 6.2 release.

Some background related to puppet-environment related changes between Satellite6.1 and Satellite6.2.

Earlier with Satellite6.1: 

1) Puppet Environment (kt_<env>) was created for every Content-Views even if no puppet modules were added 
to the Content-Views.
2) So, when puppet-foreman_scap_client RPM was installed  under /usr/share/puppet/modules/ it was automatically 
made available to all the puppet environments.
3) The puppet environment is visible in the select box, during the "new host" page.
4) This I believe helped the puppet-class 'foreman_scap_client' available for all the "Hosts", irrespective of CV or the puppet-environment.


Now with Satellite6.2/Nightlies:

1) Puppet Environments (kt_<env>) are created only if Content-views contains any "puppet modules" in it. 

2) so, now when puppet module "foreman_scap_client" is installed.

3) The puppet environment is now not visible in the select box, during the "new host" creation , due to the changes mentioned as per 1).

The Problem:

4) So now, asking the user to add "foreman_scap_client" puppet-module to every CV would be difficult to handle for OSCAP functionality.

Below Updation Required:
---------------------------

Need updation to sat6.2 docs because of changes in work-flow, related to importing of puppet-class (puppet-foreman_scap_client) to a puppet_environment. 

5) So, create a new puppet environment via the UI "oscap_environment" and on the file-system of satellite "mkdir -p /etc/puppet/environments/oscap_environment/modules"

6) Now only after importing "foreman_scap_client" and "stdlib" class to "oscap_environment" puppet-environment, we can add 
the puppet-class to the host, via the "new host" page.

Isolated Capsule:

7) Using just one puppet_environment for both "default capsule" and "isolated capsule", doesn't work as the puppet-classes cannot be imported to the same puppet_environment.

8) So, we need to create another puppet_environment called "oscap_environment1" for  "isolated capsule" from the UI and on the file-system of capsule, run
"mkdir -p /etc/puppet/environments/oscap_environment1/modules".

9) Now only after importing "foreman_scap_client" and "stdlib" class to "oscap_environment1" puppet-environment, we can add 
the puppet-class to the host, via the "new host" page.


Additional information: 

No update required for Sat6.1 docs