New Rover features from user feature requests

[im2nguyen]

Rover v0.2.0 will address most of the issues as of Sept 27, 2020

[im2nguyen]

Commit fixes #24. Users are able to specify rover ip and port

$ rover -ipPort "0.0.0.0:9001"
2021/09/27 21:46:54 Starting Rover...
2021/09/27 21:46:54 Initializing Terraform...
2021/09/27 21:46:55 Generating plan...
2021/09/27 21:46:55 Parsing configuration...
2021/09/27 21:46:55 Generating resource overview...
2021/09/27 21:46:55 Generating resource map...
2021/09/27 21:46:55 Generating resource graph...
2021/09/27 21:46:55 Done generating assets.
2021/09/27 21:46:55 Rover is running on 0.0.0.0:9001

[im2nguyen]

Fixes #9 and #20.

There are now two functions to generate a map, one that relies on parsed Terraform configuration, the other one without. This enables rover to consume plan files only -- allowing rover to work in scenarios where it doesn't have direct access to the config (Terraform Cloud, Terragrunt, auto-generated HCL, CDKTF, etc...)

The trade off is that you don't have the granularity of the resources being separated by file name.

Rover visualization with parsed configuration (notice that resources are grouped by file name first)

Rover visualization without parsed configuration (notice how everything is grouped together)

Still need to update the UI since no-config introduces a small bug in displaying/selecting resource details

[im2nguyen]

Fixes #29. The new showSensitive defaults to false and sensitive variable and output values to "Sensitive Value".

$ rover -showSensitive=true

[im2nguyen]

Fixes #18. The new workspaceName flag allows you to select an existing Terraform CLI workspace.

$ rover  -workspaceName "development"

This flag assumes that the workspace already exists. If it doesn't, rover will throw an error.

$ rover   -workspaceName "production"
2021/09/28 02:33:46 Starting Rover...
2021/09/28 02:33:46 Initializing Terraform...
2021/09/28 02:33:46 Running in production workspace...
2021/09/28 02:33:46 Unable to parse Plan: Unable to select workspace (production): workspace "production" does not exist
exit status 1

[im2nguyen]

Fixes #28.

There was a bug whenever an output or a resource referenced another resource's attribute.

[im2nguyen]

Fixes #35. The current/proposed state for output was wonky if the value was a string.

[im2nguyen]

Fixes #32 (comment) UI bug

Still need to update the UI since no-config introduces a small bug in displaying/selecting resource details