Enable OCLI and Composer extract/create commands to append output to an existing file

Currently, when using OCLI or Composer to extract multiple object types, each extract operation requires its own output file. As a result, users must execute multiple extract commands and manage multiple files before performing a subsequent add or replace operation.

For example, a user may need to extract several different object types from an environment. Due to current file handling limitations, each object type must be written to a separate file, resulting in a collection of intermediate files that must later be consolidated or processed individually.

Requested Enhancement:

Provide an option within the OCLI and Composer extract/create functionality to append output to an existing file rather than requiring the creation of a new file for each command execution.

Possible implementations could include:

• An ;append option for extract commands.
• An append mode for create commands when an output file already exists.
• A configurable parameter that allows output to be either:
  • Create/overwrite file (current behavior)
  • Append to existing file

This enhancement would allow users to perform multiple extract operations and continuously add the results to a single output file. The individual extract commands would still be subject to their existing object type restrictions and syntax requirements, but users would no longer need to manage multiple output files.

Once all desired objects have been collected into a single file, users could perform a single add or replace operation against the target environment, simplifying deployment and migration workflows.

By enabling an append option, users could consolidate related objects into a single deployment artifact, resulting in a more streamlined, maintainable, and user-friendly workflow while preserving the existing object-specific extraction behavior.