Implement project delete subcommand

[sonofachamp]

Overview

project delete should orchestrate deletion of all resources associated with a project.

This includes:

• apps
• environments
• stack set instances
• stack set
• infrastructure roles

All of these resources are CloudFormation managed, so it should be a matter of orchestrating the proper sessions and clients to accomplish deletion.

Inputs

Project name

NOTE: Currently env delete requires a profile to be input. Following a similar approach of using the "default" profile is probably sufficient for the first pass implementation of project delete.

Prompting for project name shouldn't be necessary since this command can only be supported from a local workspace which means we should be able to derive a project name.

Deletion confirmation

A --confirm or --yes flag will be supported to bypass a deletion confirmation prompt.

Flow

NOTE: Deletion order is significant.

• delete apps
• delete stack set instances
• delete stack set
• delete environments
• delete SSM param
• delete local workspace folder

I don't know of an existing way to detect application deployments to specific environments, but it's safe to assume the CloudFormation stack names, so we can do existence checks for stacks named <project>-<env>-<app> to confirm an existing deployment, or we could potentially just fire off stack deletions and gracefully handle failures when the stack doesn't exist (app isn't deployed).