Parse mdaa --testing stdout into the structured, normalized command list.
mdaa prints each CDK command across multiple physical lines joined with the
separator ' \\\n\t' (see MdaaDeploy.createCdkCommand). A logical command
therefore starts on a line beginning with npx/cd and continues on the
following tab-indented lines for as long as the previous line ends with a
trailing backslash. Those continuation lines carry the meaningful CDK context
(-c 'org=...', module_config_data, permissions_boundary_arn, role ARNs,
etc.), so they must be folded into one logical command before diffing —
otherwise the baseline only captures the first line and cannot detect drift in
any context parameter.
Parse mdaa --testing stdout into the structured, normalized command list.
mdaa prints each CDK command across multiple physical lines joined with the separator
' \\\n\t'(see MdaaDeploy.createCdkCommand). A logical command therefore starts on a line beginning withnpx/cdand continues on the following tab-indented lines for as long as the previous line ends with a trailing backslash. Those continuation lines carry the meaningful CDK context (-c 'org=...',module_config_data,permissions_boundary_arn, role ARNs, etc.), so they must be folded into one logical command before diffing — otherwise the baseline only captures the first line and cannot detect drift in any context parameter.