1. Proposed title of this feature request

Show a message or warning if custom-hiera.yaml or custom answers file is being used by satellite-installer

2. What is the nature and description of the request?

A change in installer\foreman_maintain code to show a message\warning ( in bold ) about the usage of custom-hiera or any custom answers file.

3. Why does the customer need this? (List the business requirements here)

• custom-hiera.yaml: The user can mention many things here which are or mainly aren't possible to achive via installer options and hence the end-user needs to know if satellite is inheriting any values\settings mentioned in custom-hiera.yaml file. We don't need to be specific but we can definitely tell users that they have something defined in the same file which will be considered by installer.

• Custom Answers file: Satellite by-default comes with /etc/foreman-installer/scenarios.d/satellite-answers.yaml file but we also support users to define and use their own answers file. Sometimes, when we leave things in user's control, They can remove certain important options from the answers file which may be required for future upgrades but such attempts would fail due to having those missing answers\options or their wrong values.

Example: Pulp2-Pulp3 migration fails\completes witout performing anything i.e.
~~
Prepare content for Pulp 3:
Checking for valid Katello configuraton.
Switchover is already complete, skipping migration work.
[OK]
~~

And this is because the user have wrong values set for the required options in their custom answers file. Support case 03301603 ( Comment 50 and above ) is a good example of how things can easily take a weird turn.

4. How would the customer like to achieve this? (List the functional requirements here)

RH Support only requests here to add a warning\message ( in bold ) whenever some valid yaml block is present in custom-hiera or a custom answers file is used by installer.

5. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.

Depends on Point 4 but

6. Is there already an existing RFE upstream or in Red Hat Bugzilla?

No, as far as I can say

7. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?

As soon as it is feasible.

8. Is the sales team involved in this request and do they have any additional input?
No.

9. List any affected packages or components.

• foreman-installer
• satellite-installer

10. Would the customer be able to assist in testing this functionality if implemented?

RH Support can

11. Additional information:

NA