As a Satellite Admin I have a foremanctl command (suggestion: foremanctl prepare)

Command input:
A data structure containing:

• answers file
• configuration files (the files with DB credentials and other configuration information that is not in the answers file)
• certificates
• database backup / pointer to the archive (optional, in case we want to restore data from a backup)

The command is responsible for:

• analyze the input for problems
• analyze the input for missing information
• analyze the input for conflicts
• ask the user for resolving conflicts and adding the missing information
• ignore unchanged default values
• transform the original data + user inputs into a new data structure format
• generating a report with all the changes that were made by the transformation: ignored properties, renamed properties, resolved conflicts

Command output:

• A data structure that is readable by the foremanctl deploy command that contains all the information needed to deploy a system with the same configuration as the original one.

Notes:

• see SAT-38734 for some PoC grade code
• https://github.com/theforeman/foremanctl/blob/master/docs/parameters.md has a list of existing parameters that can be mapped already
• not all parameters are part of the "kafo answers" (/etc/foreman-installer/scenarios.d/scenario-answers.yaml) and need to be obtained differently
• the translation list needs to be easily editable, as we're still in the process of adjusting parameters
• I suggest the tool will use the paths to the config files relative to / folder with a way to specify the relative root. This way we will be able to read the configuration files from the known and familiar location, and if we go the restore way, we will extract the backup into a folder (let's say /tmp) and there we will see the same file structure as in the live system.