Terraform workspace is left behind after an `atmos terraform destroy`

Have a question? Please checkout our [Slack Community](https://slack.cloudposse.com) or visit our [Slack Archive](https://archive.sweetops.com/).

[](https://slack.cloudposse.com)

## Describe the Feature

When an `atmos terraform destroy` is run without a target, once all the resources are successfully destroyed, the workspace should also be removed.

https://www.terraform.io/cli/commands/workspace/delete

```
# switch to the default workspace
terraform workspace select default
# finally delete the old workspace
terraform workspace delete
```

Perhaps this can also be another input configuration var in atmos.yaml

Start at the implementation of `atmos terraform destroy` and trace the no-target path after resources are removed. Consult Terraform's workspace select and delete commands, then verify that the destroyed stack workspace is removed while the default workspace remains available. Done means an un targeted destroy cleans up the workspace without affecting targeted destroys.

Written by the indexing model from the issue text.