Feature Overview (aka. Goal Summary)  

Allow users to install OpenShift without deleting their configuration input from the filesystem. 

Goals (aka. expected user outcomes)

At first, this should take the form of an optional command-line flag, so as not to break any automation that relies on this. In a future release, this can be made the default. A second flag, introduced at the same time as the first one, will allow users to continue with the legacy behaviour.

Requirements (aka. Acceptance Criteria):

OpenShift Installer configuration files will be preserved for bootstrapped clusters instead of automatically deleting these files if the user opts to do so

Anyone reviewing this Feature needs to know which deployment configurations that the Feature will apply to (or not) once it's been completed.  Describe specific needs (or indicate N/A) for each of the following deployment scenarios. For specific configurations that are out-of-scope for a given release, ensure you provide the OCPSTRAT (for the future to be supported configuration) as well.

Background

Installing OpenShift frequently requires a period of iteration on the install-config. Since the installer currently deletes its inputs, every piece of documentation we have requires the user to back up the install-config (and other inputs) before running the installer. This complicates the documentation, makes the user dependent on written documentation and tribal knowledge (vs. using interactive help), creates unnecessary extra work for the user, and is error-prone as they may easily forget to backup after making changes.

Documentation Considerations

Usual documentation will be provided to instruct the users about this new installation option