The proposed content requires very few changes to the current Adding custom manifests section.

Do not create a new assembly. Use the existing custom manifest assembly and change the title and its contents.

Task scope:

• New concept module: About patching manifests. This is for both the UI and API assemblies, so it does not matter who writes it, as long as the module is used in both places.
• New procedure module: Creating a patch. This is for both the UI and API assemblies because it can only be done from the CLI. So use a single module.
• Upload patch: Use the existing "Uploading custom manifests" procedure module, update it so that it includes patches and custom manifests, and split step 4 into 2 steps:

• • To upload a custom manifest....
  • To patch a manifest ....

People:

SME: Paul Maidment

QE: TBD

Background:

It is now possible to upload, replace and delete patch manifests in addition to custom manifests. The purpose of a patch manifest is to patch manifests automatically created by assisted-installer during installation preparation.

Documentation Updates (Day 1): 

• Add a new subsection 4.12 Adding patch manifests to the Assisted Installer Guide after section 4.11 Adding custom manifests: https://access.redhat.com/documentation/en-us/assisted_installer_for_openshift_container_platform/2024/html/installing_openshift_container_platform_with_the_assisted_installer/installing-with-api#adding-custom-manifests_installing-with-api

• Also add a procedure for identifying and showing the content of system generated files, according to commands in image below:

Resources and Links:

Take the information from Paul's PR: https://gitlab.cee.redhat.com/pmaidmen/assisted-installer-saas-documentation/-/merge_requests/1/diffs

Release Note

No