Deploy & other basic commands

[joshmarsh]

Goal

POC the core functionality of the CLI.

Important Notes

• I intend to clean up the code more as I start writing tests. We've gone back and forth a bit on CLI requirements recently, and there was a lot of discovery work involved in this. Therefore I neglected proper error handling, logging, and testing in favor of putting more functionality into the POC so as to drive alignment.
• The markdown files are autogenerated. I suggest using the file filter to filter them out.
• I'm continuing to look into patterns for inversion of control and dependency injection in go. The current solution was a bit rushed. Suggestions are welcome.

Current Functionality:

1. dce init uses an interactive prompt to generate a config file
2. dce deploy deploys dce to a new master account based on credentials in the config file. Terraform and code artifacts are downloaded from the latest github release.
3. dce auth opens a web browser to the authentication (SSO) url provided in the config file. User is instructed to login and then copy/paste their API credentials into the terminal. This is not yet integrated with the backend auth solution.
4. dce accounts add --account-id <string> --admin-role-arn <string> adds an existing account to the accounts pool Bug: The codebuild reset is currently failing to trigger on master accounts deployed by the cli.
5. dce leases create --budget-amount <float> --budget-currency <string> --email <stringArray> --principle-id <string> creates a lease
6. dce leases login [--account-id <string> | --lease-id <string>] --open-browser returns temporary credentials for a leased account. Opens a browser to the console if the --open-browser flag is present. This is not yet integrated with the backend auth solution.
7. dce leases end --account-id <string> --principle-id <string> ends a lease
8. dce accounts remove --account-id <string>

Next Steps:

1. Fix codebuild reset bug
2. Integrate auth & lease login
3. Write tests and create CI/CD for this repo
4. Implement remaining functionality. I would like to explore autogenerating dce deploy flags/interactive prompt from variables.tf and API client code/commands from swagger.

[marinatedpork]

@kddejong, @joshmarsh - Let's call this sufficient as a POC. Please have tests and error handling as a follow up in your coming PR.