With EAP7-574, a way to pass files from path as input stream index through CLI to operation was enabled. While the name and type is technically correct, this process should be completely transparent to user. The name, description and type of the parameter is quite unintuitive and hard to associate with file path:

"input-stream-index" => {
    "type" => INT,
    "description" => "The index into the operation's attached input streams of the input stream that contains deployment content that should be uploaded to the domain's or standalone server's deployment content repository.",
    "expressions-allowed" => false,
    "nillable" => true,
    "alternatives" => [
        "hash",
        "bytes",
        "url",
        "path",
        "relative-to",
        "empty"
    ],
    "min" => 1L,
    "max" => 2147483647L,
    "filesystem-path" => true,
    "attached-streams" => true
}

Suggested improvements

• Change the parameter name to source-path to be consistent with target-path in /deployment=deployment.jar:add-content operation.
• Change the parameter type to STRING.
• Write up a suitable description.
• Since it was impossible to properly pass the input-stream-index parameter in CLI, all the changes mentioned should be committed only in the way this is rendered in CLI, not in the model. Changes in model could break the backwards compatibility, since it was possible to pass the input-stream-index through native management in previous versions.