Feature #3483
closed
Pre-packaged default answers file
Description
One thing that can confuse a new user is the huge growth that happens to the answers file after running the installer.
Impressive though the installer is, it might be an idea to package a default.answers file just to illustrate what the answers file will look like after a default run. Users can then diff their own file against this to see what is different from the default set.
Updated by Duncan Innes over 10 years ago
Just to clarify - this should be a fully expanded default.answers file.
Updated by Duncan Innes over 10 years ago
Also meant this to be a feature rather than a bug.
Updated by Dominic Cleal over 10 years ago
- Tracker changed from Bug to Feature
- Category set to foreman-installer script
Updated by Marek Hulán over 10 years ago
I think it's not a good idea. Some parameter values may vary on different systems. I don't say there is such at the moment but once they appear it's easy to forget. When values are stored in answer file they don't adapt anymore. What we can do is to provide some example files (for various systems if needed).
Updated by Duncan Innes over 10 years ago
Example answers files for various deployment types would also be a great idea.
Anything where the user can see the possible default values is better than nothing. Having experienced this myself and seen other SysAdmins confused at the answers file after running the installer, I think it's a problem that could do with a solution. Whether this is the right way to solve it - don't know. Is a default answers file not an extension of the example files, expanded to show all the defaults?
Updated by Anonymous about 7 years ago
- Status changed from New to Resolved
The original request is IMHO not fulfilable, the other is covered by installer scenarios now.