Comment 6 for bug 1557888

Alas, the feedback message behavior for different commands is inconsistent. One reason is because of the utils.do_action_on_many function that's used in some commands to enable the command to run in a batch (for example, 'nova delete server1 server2 server3'). The utils.do_action_on_many prints a message to the screen for each resource it acts upon.

I notice some commands arbitrarily have feedback even though they don't run in a batch. Many commands don't have any feedback.

I'm not aware that there has been any strategy around command feedback messages.

There was recently some effort to add the batch ability to more commands with a blueprint [1] and a patch [2] up.

But that got stalled on opposition to the idea of adding more feedback messages without placing them behind a --verbose flag.

The problem is there are already a lot of feedback messages that are not behind a --verbose flag. So we either should put them all behind --verbose flags or just add the new messages as-is. That is, I think it should be consistent.

Either way is not a fun situation IMO because you either have a release where all feedback messages disappear suddenly and need --verbose to get them back or you have new feedback messages unexpectedly showing up for some commands in the release. Or, you can be inconsistent and not have new unexpected printing but new feedback messages go behind --verbose. I just thought it would be confusing if some commands need --verbose to see feedback and some don't.

Thoughts?

[1] https://blueprints.launchpad.net/python-novaclient/+spec/enhance-commands-for-usability
[2] https://review.openstack.org/#/c/190111/