Created attachment 1950247 [details]
Provisioning form with highlighted Puppet configuration fields

Description of problem:

During host Registration, Puppet integration between the host and Satellite can be configured using host parameters (puppet_server, puppet_ca_server, puppet_environment). This configures the Puppet agent on the host, but it doesn't configure the Puppet integration in Satellite. For example, Satellite does not know to which Puppet environment the host belongs. The user has to take additional steps to assign the environment after the host is registered before they can start assigning Puppet classes.

It would be more user-friendly if Puppet was configured during Registration the same way as during the Provisioning process. The user should be able to select Puppet CA Capsules and the Puppet environment from a dropdown menu in the Registration form or using variables in CLI or API. This should configure both the Puppet agent on the host and the integration in Satellite. At the same time, these values can be inherited from a host group.

The host parameters are meant to configure the Puppet agent for non-integrated setups.

Version-Release number of selected component (if applicable): N/A


How reproducible: always


Steps to Reproduce:
1. Configure host parameters puppet_server and puppet_ca_server using the hostname of Puppet and Puppet CA Capsule as values, and puppet_environment
2. Register a host

Actual results:
Puppet agent is configured, but Satellite is not aware of the Puppet configuration on the host

Expected results:
Satellite should be aware of the Puppet configuration on the host, especially the Puppet environment, after Registration without the user having to take additional steps

Additional info:

Screenshot of the Provisioning form ("Create Host") attached for illustration.
Let's add a similar set of fields to the "Register Host" form and corresponding variables to CLI and API.
This is mainly about improving the UX workflow.