Merge branch 'gitlabBugWorkaround' into '2.8.2.1-DEVELOMENT'

No Story: Truncating ingest-envoy README.

See merge request !1532

apps/cli/executables/pexable/ingest_envoy/README.md

@@ -24,9 +24,6 @@ Ingest Envoy makes use of the existing *ingest* functionality of the AAT-PPI whi
 as well as the ingestion staging requirements differ between the types of files to be ingested. For this reason,
 Ingest Envoy's functionality can be broken into two underlying parts: Setup and Launch.
 
-## Setup
-Setup can be further divided into two essential components: Product Staging and Manifest Generation.
-
 ### Product Staging
 Product Staging is the step that collects all ingestable products and places them in the workspaces staging area located at:
 ``` /lustre/aoc/cluster/pipeline/<capo-profile>/workspaces/staging ```
@@ -65,12 +62,3 @@ and the pipeline and ingestion artifacts tar files.
 
 After the manifest is properly generated, the manifest and any additional metadata files are tarred up into the
 *ingestion artifacts* tar file and both the manifest and the new artifact tar file are placed in the staging area.
-
-## Launch
-Calibration and Image ingestion are initiated in exactly the same way - by providing the staging area directory name to
- *ingest*. Because of this, Ingest Envoy contains a single function for launching the *ingest* pex which is called by
-all typed ingestion launchers.
-
-Ingest Envoy has two types of Launcher classes: IngestCalibrationLauncher and IngestImageLauncher. Each typed launcher
-handles the type specific setup, as described above, and then call the shared ingestion function. Upon *ingest*'s
-completion, Ingest Envoy checks the return code and logs either a successful or failed ingestion and exits.