Comment 2 for bug 1378837

We don't want to have an additional 'abort' action for each state we're in, nor an additional API for aborting each state we're in.

This action should eventually replace the 'Abort Commissioning' operation and should be extended to work for other operations too. There is a corresponding 'abort_operation' call on the API already too.

re: kiko's comment. I'm not sure how you could get away with not having an 'Abort' action/API call - there needs to be a way for a user to cancel this potentially very long running operation. We don't have any plans right now to get rid of this, that I know of.