When using the stack abandon I find that not having a default output file to hold the state makes this a dangerous operation. If the user prematurely issues the command without redirecting the output of "heat stack-abandon" to a file then they loose the state information, and there is no other way to recover it. This command should have something akin to a "-o" option to specify the name of the output file, with a default when not specified (e.g. if we issue "heat stack-abandon test-stack", and did not specify an output file with "-o", then produce a file "test-stack.state", or something to that effect"). The option to output to standard out may be useful, so maybe we still want to have a way to tell this command to output to stdout (e.g. a file name "-" for "-o"?).
Is this still valid? Stack-abandon prints to stdout by default (https:/ /github. com/openstack/ python- heatclient/ blob/master/ heatclient/ v1/shell. py#L262), so if user has forgot to redirect the output (s)he is still able to copy-paste from terminal.