CLI using the API

Registered by Tim Penhey

Tracking the conversion of all the juju command line sub-commnands to use the API instead of direct mongo connections.

Photo of the breakdown: http://people.canonical.com/~tim/api-cli.jpg

Blueprint information

Status:
Complete
Approver:
Tim Penhey
Priority:
Essential
Drafter:
Tim Penhey
Direction:
Approved
Assignee:
None
Definition:
Approved
Series goal:
None
Implementation:
Implemented
Milestone target:
None
Started by
Tim Penhey
Completed by
Dimiter Naydenov

Related branches

Sprints

Whiteboard

Keeping the todo items at the top, followed by in progress. Done at the end for easier scanning.

sync-tools needs discussion as to whether it needs to go via the api or not.

(?)

Work Items

Work items:
api-endpoints should use API rather than Env access: TODO
deploy: DONE
status: DONE
upgrade-charm: DONE
destroy-environment: DONE
upgrade-juju: DONE
add-machine: DONE
add-relation: DONE
add-unit: DONE
debug-hooks: DONE
debug-log: DONE
destroy-machine: DONE
destroy-relation: DONE
destroy-service: DONE
destroy-unit: DONE
expose: DONE
get: DONE
get-constraints: DONE
get-environment: DONE
init: DONE
help: DONE
help-tools: DONE
resolved: DONE
scp: DONE
set: DONE
set-constraints: DONE
set-environment: DONE
ssh: DONE
unexpose: DONE
unset: DONE
sync-tools N/A doesn't use Conn, just direct Env access: DONE

This blueprint contains Public information 
Everyone can see this information.