TODO

A set of targets/milestone features that I'd like to see implemented into production, separated into MUST HAVE, SHOULD HAVE, COULD HAVE, and WON'T HAVE. (See more at the MoSCoW method).

Must Have

View all owned apps
- View all apps that the user has access to (needs to be confirmed)
View all owned pipelines
View the states of Dynos
Alter the states of Dynos (you can do this by scaling)
View what addons are connected to an app
Connect a one-off dyno to an app
Trigger a build from the workspace root
- This should only be available if the user has a heroku git remote
Addon management
- Provision new addons
- Remove addons
Fix the bug where the tree doesn't load in a timely manner
- Even better: have it lazy load and show some tree item results as they respond

View the app logs of specific Dynos
- View any type of log for specific Dynos
- Use the log terminal pane to switch
Push and build an app (and view it's build log)
Make more options configurable (such as dyno TTL)
View the Config Vars for a specific app
- Be able to update those Config Vars
- Edit Config Vars in a custom editor (maybe?)
  - This would allow us to hook into the save event without VSCode getting angry at us if the user doesn't want to actually save the file? (https://code.visualstudio.com/api/extension-guides/custom-editors#custom-text-editor)

Set the context of the treeview to a particular app or pipeline
- Make it persistent to the project (use machine-overridable?)
Change the dyno.create command location to be an element in the Dyno Tree
Better views (maybe WebViews) for responses from the server taht pretty much get piped directly to the user