Does not distinguish between templates and instance units about fleet-api

[bdehamer]

From my investigation, it looks like the template stuff is really a feature of the fleetctl client and not the API itself. If you do something like fleetctl start [email protected] it results in API traffic that looks like this:

GET /fleet/v1/units/[email protected] // which results in a 404
GET /fleet/v1/units/foo@service 
PUT /fleet/v1/units/[email protected]
GET /fleet/v1/units/[email protected] // 200, this time

Basically, fleetctl will pull down the template and then turn around and submit it as a new unit with the specified name.

Would welcome a PR if someone wants to take a crack at implementing something like this.

[robholland]

Recent fleet versions now prevent you from trying to start a template unit. We had so much pain with this, so easy to accidentally do it. I think you can close this, fleet will do the right thing (return an error).

[bdehamer]

@robholland, thanks for the update. Gonna close this issue.