Epic Goal

• Allow users to install OpenShift without deleting their configuration input from the filesystem. 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.

Why is this important?

• 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.

Scenarios

1. ...

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

Open questions::

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>