For some reason there's two spaces between cancel and <identifier>.

Also, I'm considering how to handle the need for --cci, --vlan, --server better. I noticed this same pattern in the load balancer stuff as well. The problem as I see it is that you need to be able tell what type of firewall it is before being able to cancel it, detail it, etc. I feel like requiring more than an id from someone to do these kinds of things is a bit at least intuitive if not confusing.

I have 3 proposals:
1. encode the type of the object in the id. E.G.: cci:1234, vlan:5678, server:0987
2. do (at least) 3 additional API calls in order to determine the type of thing. If a customer happens to have two ids of the same
3. instead of making it a CLI flag (which are ~typically~ optional) make it an extension of the command. E.G.: sl fire wall cancel hardware 1234. The usage would look something like the following:
```bash
usage: sl firewall cancel cci <identifier> [options]
       sl firewall cancel vlan <identifier> [options]
       sl firewall cancel server <identifier> [options]
```